Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

USB devices inside Virtualbox (Windows) guest VM are not usable #1615

Closed
1 task done
Wini-Buh opened this issue Feb 14, 2024 · 2 comments
Closed
1 task done

USB devices inside Virtualbox (Windows) guest VM are not usable #1615

Wini-Buh opened this issue Feb 14, 2024 · 2 comments
Labels
Bug Something isn't working

Comments

@Wini-Buh
Copy link

Summary

Since the last update (week 6, 2024) on any of my Windows guests VMs, I don't have access to any of the connected USB devices (mostly I use JTAG emulators). I also tried to access USB memory sticks, a FTDI USB-UART cable, etc. (in other words USB devices I'm 100% sure that they worked in the past). No of them could be accessed from inside the VM.
I'm quite sure this is since the latest kernel update, because I use a VM with a Win10 guest on every workday, for embedded software development.

Steps to reproduce

  1. Start a Windows guest VM
  2. Insert a USB device which you would like to access in the VM
    3a. If the USB device is automatically connected try to access it
    or
    3b. If the USB device is not automatically connected, then connect it over the USB icon on the Virtualbox status line and try to access it

Expected result

The connected USB device is usable in the guest VM

Actual result

The USB devices are not usable in the guest VM at all

Environment

  • Is system up to date?

Repo

Shannon (stable)

Desktop Environment

Budgie

System details

System:
  Host: winformatikpc Kernel: 6.6.16-273.current arch: x86_64 bits: 64
    Desktop: Budgie v: 10.9.1 Distro: Solus 4.5 resilience
Machine:
  Type: Desktop Mobo: Intel model: DH87RL v: AAG74240-403
    serial: <superuser required> UEFI: Intel v: RLH8710H.86A.0332.2018.1026.1448
    date: 10/26/2018
CPU:
  Info: quad core Intel Core i5-4570 [MCP] speed (MHz): avg: 798
    min/max: 800/3600
Graphics:
  Device-1: AMD Bonaire XT [Radeon HD 7790/8770 / R7 360 R9 260/360 OEM]
    driver: amdgpu v: kernel
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
    resolution: 3840x2160~30Hz
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.5 renderer: AMD
    Radeon HD 7700 Series (radeonsi bonaire LLVM 16.0.6 DRM 3.54
    6.6.16-273.current)
Network:
  Device-1: Intel Ethernet I217-V driver: e1000e
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  Device-3: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
Drives:
  Local Storage: total: 476.94 GiB used: 335.6 GiB (70.4%)
Info:
  Processes: 274 Uptime: 3h 32m Memory: total: 32 GiB available: 31.3 GiB
  used: 24.61 GiB (78.6%) Shell: Bash inxi: 3.3.31

Other comments

Virtualbox version: 7.0.14_Solus r161095
@Wini-Buh Wini-Buh added the Bug Something isn't working label Feb 14, 2024
@Wini-Buh
Copy link
Author

Still no USB devices available inside the Virtualbox (Windows) guest VMs after today's update (week 6). Having the problem on several different Solus Budgie installations. The VMs worked all well before the update around the week 4 or 5.

As soon as I start a VM I'm seeing this in the system log :

Feb 17 08:44:54 solus-pc kernel: SUPR0GipMap: fGetGipCpu=0x3b
Feb 17 08:44:55 solus-pc kernel: ------------[ cut here ]------------
Feb 17 08:44:55 solus-pc kernel: WARNING: CPU: 10 PID: 5554 at /home/build/YPKG/root/virtualbox/build/VirtualBox-7.0.14/out/linux.amd64/release/bin/6.6.16-275.current/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:564 rtR0MemObjLinuxApplyPageRange+0x5b/0xb0 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_mangle vboxnetadp(O) iptable_nat vboxnetflt(O) nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter ip_tables x_tables bridge stp llc vboxdrv(O) qrtr bnep intel_rapl_msr snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir intel_rapl_common snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp mt7921e mt7921_common snd_sof mt792x_lib snd_sof_utils btusb snd_hda_codec_hdmi edac_mce_amd mt76_connac_lib btrtl snd_soc_core btintel mt76 snd_hda_intel btbcm snd_compress kvm_amd btmtk snd_intel_dspcfg snd_intel_sdw_acpi ac97_bus mac80211 snd_usb_audio snd_pcm_dmaengine kvm snd_hda_codec snd_pci_ps snd_usbmidi_lib snd_rpl_pci_acp6x bluetooth snd_ump snd_acp_pci irqbypass snd_hda_core snd_acp_legacy_common snd_rawmidi snd_pci_acp6x snd_hwdep snd_seq_device ecdh_generic rapl acpi_cpufreq i2c_piix4 k10temp
Feb 17 08:44:55 solus-pc kernel:  joydev snd_pcm r8169 snd_pci_acp5x cfg80211 snd_timer snd_rn_pci_acp3x realtek snd_acp_config igc mc mdio_devres snd_soc_acpi snd ptp snd_pci_acp3x rfkill soundcore pps_core libarc4 libphy cm32181 industrialio evdev sch_fq_codel msr fuse configfs hid_logitech_hidpp hid_logitech_dj hid_cmedia usbhid amdgpu drm_exec amdxcp drm_buddy gpu_sched drm_ttm_helper ttm i2c_algo_bit drm_suballoc_helper drm_display_helper sd_mod xhci_pci crct10dif_pclmul cec nvme xhci_pci_renesas crc32_pclmul i2c_hid_acpi xhci_hcd polyval_clmulni drm_kms_helper i2c_hid ahci polyval_generic nvme_core usbcore ghash_clmulni_intel nvme_common sp5100_tco libahci amd_sfh ccp usb_common t10_pi video wmi drm
Feb 17 08:44:55 solus-pc kernel: CPU: 10 PID: 5554 Comm: EMT-0 Tainted: G           O       6.6.16-275.current #1
Feb 17 08:44:55 solus-pc kernel: Hardware name: BESSTAR TECH LIMITED HM90/HM90, BIOS 5.16 10/13/2021
Feb 17 08:44:55 solus-pc kernel: RIP: 0010:rtR0MemObjLinuxApplyPageRange+0x5b/0xb0 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel: Code: 83 e6 42 48 c1 e0 0c 48 83 fe 40 74 1d 48 85 d2 75 1a 48 ba 00 f0 ff ff ff ff 0f 00 5d 48 21 d0 48 89 01 31 c0 e9 25 21 47 e0 <0f> 0b f6 c2 01 75 1e 48 be 00 f0 ff ff ff ff 0f 00 48 f7 d0 5d 48
Feb 17 08:44:55 solus-pc kernel: RSP: 0018:ffffc90006393ca8 EFLAGS: 00010246
Feb 17 08:44:55 solus-pc kernel: RAX: 0000000266092000 RBX: ffffc90007200000 RCX: ffff8882452965f0
Feb 17 08:44:55 solus-pc kernel: RDX: 0000000000000161 RSI: 0000000000000040 RDI: ffff888100eac010
Feb 17 08:44:55 solus-pc kernel: RBP: ffffc90006393ca8 R08: ffffffffa1a25c60 R09: ffffc90006393e10
Feb 17 08:44:55 solus-pc kernel: R10: 0000000000000000 R11: ffffc980070be000 R12: ffffc90006393e10
Feb 17 08:44:55 solus-pc kernel: R13: 0000000000000001 R14: ffffc900070be000 R15: ffff8882452965f8
Feb 17 08:44:55 solus-pc kernel: FS:  00007f182c17e6c0(0000) GS:ffff8887ef680000(0000) knlGS:0000000000000000
Feb 17 08:44:55 solus-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 17 08:44:55 solus-pc kernel: CR2: 00007f17e8d5a000 CR3: 000000022d400000 CR4: 0000000000350ee0
Feb 17 08:44:55 solus-pc kernel: Call Trace:
Feb 17 08:44:55 solus-pc kernel:  <TASK>
Feb 17 08:44:55 solus-pc kernel:  ? rtR0MemObjLinuxApplyPageRange+0x5b/0xb0 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  ? __warn+0x7d/0x130
Feb 17 08:44:55 solus-pc kernel:  ? rtR0MemObjLinuxApplyPageRange+0x5b/0xb0 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  ? report_bug+0x18d/0x1c0
Feb 17 08:44:55 solus-pc kernel:  ? handle_bug+0x3a/0x70
Feb 17 08:44:55 solus-pc kernel:  ? exc_invalid_op+0x13/0x60
Feb 17 08:44:55 solus-pc kernel:  ? asm_exc_invalid_op+0x16/0x20
Feb 17 08:44:55 solus-pc kernel:  ? __pfx_rtR0MemObjLinuxApplyPageRange+0x10/0x10 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  ? rtR0MemObjLinuxApplyPageRange+0x5b/0xb0 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  ? srso_return_thunk+0x5/0x10
Feb 17 08:44:55 solus-pc kernel:  ? __pfx_rtR0MemObjLinuxApplyPageRange+0x10/0x10 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  apply_to_pte_range+0xa8/0x230
Feb 17 08:44:55 solus-pc kernel:  apply_to_pmd_range+0xec/0x220
Feb 17 08:44:55 solus-pc kernel:  ? __pfx_rtR0MemObjLinuxApplyPageRange+0x10/0x10 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  ? srso_return_thunk+0x5/0x10
Feb 17 08:44:55 solus-pc kernel:  __apply_to_page_range+0x137/0x2e0
Feb 17 08:44:55 solus-pc kernel:  ? __pfx_rtR0MemObjLinuxApplyPageRange+0x10/0x10 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  rtR0MemObjNativeProtect+0x9c/0x110 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  VBoxHost_RTR0MemObjProtect+0x87/0xc0 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  supdrvIOCtl+0x2ca9/0x31b0 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  ? srso_return_thunk+0x5/0x10
Feb 17 08:44:55 solus-pc kernel:  VBoxDrvLinuxIOCtl_7_0_14+0x165/0x260 [vboxdrv]
Feb 17 08:44:55 solus-pc kernel:  __x64_sys_ioctl+0x93/0xd0
Feb 17 08:44:55 solus-pc kernel:  do_syscall_64+0x3b/0x90
Feb 17 08:44:55 solus-pc kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Feb 17 08:44:55 solus-pc kernel: RIP: 0033:0x7f185ed1b51f
Feb 17 08:44:55 solus-pc kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
Feb 17 08:44:55 solus-pc kernel: RSP: 002b:00007f182c17cd20 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Feb 17 08:44:55 solus-pc kernel: RAX: ffffffffffffffda RBX: 0000000000000030 RCX: 00007f185ed1b51f
Feb 17 08:44:55 solus-pc kernel: RDX: 00007f17e8a99010 RSI: 0000000000005684 RDI: 0000000000000007
Feb 17 08:44:55 solus-pc kernel: RBP: 00007f182c17cd80 R08: 0000000000000000 R09: 00007f182c17cc00
Feb 17 08:44:55 solus-pc kernel: R10: 00007f17e8a99010 R11: 0000000000000246 R12: 00007f180ed35dbf
Feb 17 08:44:55 solus-pc kernel: R13: 0000000000000000 R14: 00007f17f0000ca0 R15: 0000000000000000
Feb 17 08:44:55 solus-pc kernel:  </TASK>
Feb 17 08:44:55 solus-pc kernel: ---[ end trace 0000000000000000 ]---
Feb 17 08:44:55 solus-pc kernel: vboxdrv: 00000000059eb33d VMMR0.r0
Feb 17 08:44:55 solus-pc kernel: vboxdrv: 0000000017d62eee VBoxDDR0.r0
Feb 17 08:44:55 solus-pc kernel: VBoxNetFlt: attached to 'eno1' / 1c:83:41:30:7e:fa

The VM itself is running without a problem (part from the unusable USB devices).

@Wini-Buh
Copy link
Author

Here a little screen shot of the USB menu available from the USB icon on the Virtualbox status bar (right mouse button click). For example it is not possible to connect the "Renesas E2 Lite JTAG emulator", because on all listed USB devices the buttons to activate the USB device to the VM are not available (red box).

USB_Devices_Problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Something isn't working
Projects
Solus
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Wini-Buh