[Bug 1219766] New: USB passthrough fails
https://bugzilla.suse.com/show_bug.cgi?id=1219766 Bug ID: 1219766 Summary: USB passthrough fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs@suse.de Reporter: pinkernell@ph-heidelberg.de QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- This is on OS: openSUSE Tumbleweed 20240207 Kernel: 6.7.4-1-default (64-bit) with Virtualbox 7.0.14-Virt.1699.733.2-x.86_64 Kernel module 7.0.14_k6.7.4_1-Virt.1699.733.2 Guest Windows 10, Guest Additions 7.0.14r161095 USB-3.0 xHCI Controller activated VBox host software recognises USB device (ScanSnap Scanner) and allows setting device filter. But guest does not find device. Hovering the mouse on USB icon of host software shows "No USB Devices connected". In the list of USB devices that opens after clicking on the icon, the Scanner is blanked out. This seems new since upgrade to 6.7.2(?) kernel. Which part of the log do you need? I am new here and happy to help. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c1 Mario Guzman <mario_bz@mgtech.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mario_bz@mgtech.com --- Comment #1 from Mario Guzman <mario_bz@mgtech.com> --- This happened to me after Sundays big update with new kernel and Viertualbox 7.0.14. I tried going back to previous kernel and Virtualbox 7.0.12 but no good. Today I updated to kernel 6.7.4-1 with updates and still nogo. This is a big problem since USB devices no longer work in guests after the TW updates. Others are reporting this: https://forums.opensuse.org/t/usb-grayed-out-cant-add-usb-devices-in-virtual... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 Jeffrey Cheung <jcheung@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcheung@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 Ingo Göppert <ingo.goeppert+suse@mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ingo.goeppert+suse@mailbox. | |org -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c5 Bauglir <bauglir@fsfe.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bauglir@fsfe.org --- Comment #5 from Bauglir <bauglir@fsfe.org> --- It's great to have a work-around, but those of you who make use of it should take into account that glibc 2.38 is affected by CVE 2023-6246, rated high (although it requires local access), that was fixed in 2.39. https://nvd.nist.gov/vuln/detail/CVE-2023-6246 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c12 --- Comment #12 from Ingo Göppert <ingo.goeppert+suse@mailbox.org> --- Created attachment 872660 --> https://bugzilla.suse.com/attachment.cgi?id=872660&action=edit vboxdrv kernel crash While starting a VM the vboxdrv kernel module crashes. Log is from a system with tumbleweed from today with a Win 10 VM. Same result with a Win 7 VM. A crash was also reported here https://www.virtualbox.org/ticket/21964. Both start with "memobj-r0drv-linux.c:564 rtR0MemObjLinuxApplyPageRange+0x4e/0xa0 [vboxdrv]", thus I think it is already reported upstream, but it was ignored there. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c14 --- Comment #14 from Ingo Göppert <ingo.goeppert+suse@mailbox.org> --- (In reply to Larry Finger from comment #11)
To duplicate this problem, install virtualbox 7.0.14 on a fully updated Tumbleweed host.
Download and unpack the Virtual Machine attachment file. It will show in directory home/finger/Test relative to your currrent working directory. In the VB GUI, select Machine/Add and navigate to home/finger/Test. Select "test.vbox". This step will provide a minimal VM. If you boot it, it will show that it has no bootable medium.
In this machine's screen, pull down the Devices tab and select USB. In the screen that pops up, the options are grayed out. That is the problem.
Same vboxdrv crash when starting the provided test VMN, but after that virtualbox created a segfault. I had to remove the snapshot to start up the test VM successful. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c15 --- Comment #15 from Ingo Göppert <ingo.goeppert+suse@mailbox.org> --- (In reply to Ingo Göppert from comment #14)
(In reply to Larry Finger from comment #11)
To duplicate this problem, install virtualbox 7.0.14 on a fully updated Tumbleweed host.
Download and unpack the Virtual Machine attachment file. It will show in directory home/finger/Test relative to your currrent working directory. In the VB GUI, select Machine/Add and navigate to home/finger/Test. Select "test.vbox". This step will provide a minimal VM. If you boot it, it will show that it has no bootable medium.
In this machine's screen, pull down the Devices tab and select USB. In the screen that pops up, the options are grayed out. That is the problem.
Same vboxdrv crash when starting the provided test VMN, but after that virtualbox created a segfault. I had to remove the snapshot to start up the test VM successful.
To be clear: successful but with missing USB passthru -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c17 Javier de San Pedro <javispedro@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |javispedro@gmail.com --- Comment #17 from Javier de San Pedro <javispedro@gmail.com> --- I am not sure if it is the same issue (though I started facing the same the symptoms during the glibc 2.39 migration), but could you try the following ? chmod 0660 /dev/vboxusb/*/* From what I gather from the VBoxCreateUSBNode.sh script, it is supposedly calling mknod with -m 0660 , so no idea why on my system I reproduceably find that these nodes are created with 0640 instead. Anyway, I don't fully understand how this could be even remotely caused by glibc. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c20 --- Comment #20 from Javier de San Pedro <javispedro@gmail.com> --- Thanks for confirming. I have looked a bit into it. I cannot believe this, but the issue is indeed related to glibc 2.39. glibc 2.39 has started to use the fchmodat2 syscall, which is used by mknod in the VBoxCreateUSBNode.sh to set the 0660 mode on the vboxusb nodes. However, this script is called by udevd, and the systemd unit file for udev has SystemCallFilter= enabled... but the systemd version that we have (v254) is too old to understand the fchmodat2 syscall. Therefore, mknod succeeds in creating the device node, but fails in chmod 0660'ing it, so it keeps the default 0640 due to the umask. Solution is to upgrade to systemd v255 or backport this commit https://github.com/systemd/systemd/commit/6e10405aa25fe5e76b740d9ec59730e3f4... <rant please_ignore="yes"> Yet another bug caused by an overzealous system call whitelist. As I said 3 years ago, these whitelists are my number #1 source of bugs on rolling distros. https://bugzilla.opensuse.org/show_bug.cgi?id=1190842#c8 I don't even know why we would even bother with a system call filter on udevd. It is running arbitrary shell scripts and by construction it must have kernel module loading capabilities and whatnot! What threats could a syscall filter for udevd possibly protect against ? Literally the only thing it does is complicate debugging (no ptrace!) and create issues like this. </rant> -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c22 robert spitzenpfeil <rs.opensuse@spitzenpfeil.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rs.opensuse@spitzenpfeil.or | |g --- Comment #22 from robert spitzenpfeil <rs.opensuse@spitzenpfeil.org> --- Adding chmod 0660 "$devpath" 2>/dev/null after the mknod line in said script helps for now. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c29 --- Comment #29 from OBSbugzilla Bot <bwiedemann+obsbugzillabot@suse.com> --- This is an autogenerated message for OBS integration: This bug (1219766) was mentioned in https://build.opensuse.org/request/show/1149219 Factory / systemd -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c33 --- Comment #33 from Mario Guzman <mario_bz@mgtech.com> --- Same here, AOK now. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c34 T Adams <timothyadams@ymail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |timothyadams@ymail.com --- Comment #34 from T Adams <timothyadams@ymail.com> --- The 20240223 snapshot also resolved the passthrough-to-USB-scanners issue described at: https://forums.opensuse.org/t/usb-passthrough-to-scanner-again-dead-in-tumbl.... Thanks to everyone who contributed to fixing this problem. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c35 --- Comment #35 from OBSbugzilla Bot <bwiedemann+obsbugzillabot@suse.com> --- This is an autogenerated message for OBS integration: This bug (1219766) was mentioned in https://build.opensuse.org/request/show/1152118 Factory / systemd -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c37 Thomas Rother <t.rother@netzwissen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #37 from Thomas Rother <t.rother@netzwissen.de> --- ... it seems like this strange bug reappeared again. The USB devices are gone on all vbox guests, even with the starting user being a member of "vboxusers" And the workaround from https://bugzilla.opensuse.org/show_bug.cgi?id=1219766#c17 with chmod 0660 /dev/vboxusb/*/* does not solve this anymore. Current versions are: NAME="openSUSE Tumbleweed" # VERSION="20240329" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240329" PRETTY_NAME="openSUSE Tumbleweed" Other version infos: information for package virtualbox: ----------------------------------- Repository : repo-oss Name : virtualbox Version : 7.0.14-6.1 Arch : x86_64 Vendor : openSUSE Information for package glibc: ------------------------------ Repository : repo-oss Name : glibc Version : 2.39-4.2 Arch : x86_64 Vendor : openSUSE information for package udev: ----------------------------- Repository : repo-oss Name : udev Version : 255.4-1.3 Arch : x86_64 Vendor : openSUSE I am open for any ideas to debug this ;-( ... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com