Virtualbox 7.0.1 on Leap 15.5 can not assign USB devices to guests

I recently upgraded my laptop from Leap 15.4 to 15.5. After that i can no longer assign USB devices to a guest system. I tried my iPhone and a USB memory stick. Both fail in the same way: the device doesn’t get checked in the devices list and after the try i can still see the device on the host system. Nothing happens on the guest system.

Here a snap of the hosts /var/log/messages file when i try to assign a USB stick to a Linux guest (both host and guest run Leap 15.5)

# tail -f /var/log/messages
 ...
2023-09-23T09:55:59.014798+02:00 manta (udev-worker)[27379]: sdc2: Failed to remove '/dev/disk/by-label/openSUSE-Leap-15.5-DVD-x86_64491', ignoring: No such file or directory
2023-09-23T09:55:59.015379+02:00 manta (udev-worker)[27379]: sdc2: Failed to remove/update device symlink '/dev/disk/by-label/openSUSE-Leap-15.5-DVD-x86_64491', ignoring: No such file or directory
2023-09-23T09:55:59.017472+02:00 manta (udev-worker)[27375]: sdc: Failed to remove '/dev/disk/by-label/openSUSE-Leap-15.5-DVD-x86_64491', ignoring: No such file or directory
2023-09-23T09:55:59.017762+02:00 manta (udev-worker)[27375]: sdc: Failed to remove/update device symlink '/dev/disk/by-label/openSUSE-Leap-15.5-DVD-x86_64491', ignoring: No such file or directory
2023-09-23T09:55:59.035741+02:00 manta plasmashell[9051]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/ExpandableListItem.qml:291: TypeError: Cannot read property 'enabled' of null
2023-09-23T09:55:59.084244+02:00 manta (udev-worker)[27376]: 2-2:1.0: Process '/usr/lib/snapd/snap-device-helper unbind snap_gphoto2_gphoto2 /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0 0:0' failed with exit code 1.
2023-09-23T09:55:59.355692+02:00 manta kernel: [ 9144.202807][T26553] usb 2-2: reset high-speed USB device number 6 using xhci_hcd
2023-09-23T09:55:59.503697+02:00 manta kernel: [ 9144.350736][T26553] usb 2-2: device firmware changed
2023-09-23T09:55:59.503715+02:00 manta kernel: [ 9144.351324][T26381] usb 2-2: USB disconnect, device number 6
2023-09-23T09:55:59.506665+02:00 manta (udev-worker)[27375]: 2-2: Process '/usr/lib/snapd/snap-device-helper unbind snap_gphoto2_gphoto2 /devices/pci0000:00/0000:00:14.0/usb2/2-2 189:133' failed with exit code 1.
2023-09-23T09:55:59.631785+02:00 manta kernel: [ 9144.478762][T26381] usb 2-2: new high-speed USB device number 7 using xhci_hcd
2023-09-23T09:55:59.779698+02:00 manta kernel: [ 9144.627349][T26381] usb 2-2: New USB device found, idVendor=0781, idProduct=5575, bcdDevice= 1.26
2023-09-23T09:55:59.779716+02:00 manta kernel: [ 9144.627363][T26381] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2023-09-23T09:55:59.779720+02:00 manta kernel: [ 9144.627375][T26381] usb 2-2: Product: Cruzer Glide
2023-09-23T09:55:59.779721+02:00 manta kernel: [ 9144.627376][T26381] usb 2-2: Manufacturer: SanDisk
2023-09-23T09:55:59.779722+02:00 manta kernel: [ 9144.627378][T26381] usb 2-2: SerialNumber: 200443175302E8B38D30
2023-09-23T09:55:59.779723+02:00 manta kernel: [ 9144.627884][T26381] usb-storage 2-2:1.0: USB Mass Storage device detected
2023-09-23T09:55:59.779723+02:00 manta kernel: [ 9144.628014][T26381] scsi host7: usb-storage 2-2:1.0
2023-09-23T09:55:59.785256+02:00 manta mtp-probe: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2"
2023-09-23T09:55:59.785325+02:00 manta mtp-probe: bus: 2, device: 7 was not an MTP device
2023-09-23T09:56:00.357797+02:00 manta (udev-worker)[27375]: 2-2:1.0: Process '/usr/lib/snapd/snap-device-helper bind snap_gphoto2_gphoto2 /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0 0:0' failed with exit code 1.
2023-09-23T09:56:00.361927+02:00 manta mtp-probe: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2"
2023-09-23T09:56:00.362017+02:00 manta mtp-probe: bus: 2, device: 7 was not an MTP device
2023-09-23T09:56:00.363648+02:00 manta (udev-worker)[27375]: 2-2: Process '/usr/lib/snapd/snap-device-helper bind snap_gphoto2_gphoto2 /devices/pci0000:00/0000:00:14.0/usb2/2-2 189:134' failed with exit code 1.
2023-09-23T09:56:00.787706+02:00 manta kernel: [ 9145.636254][T20707] scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Glide     1.26 PQ: 0 ANSI: 6
2023-09-23T09:56:00.787722+02:00 manta kernel: [ 9145.636681][T20707] sd 7:0:0:0: Attached scsi generic sg4 type 0
2023-09-23T09:56:00.787724+02:00 manta kernel: [ 9145.637578][T27235] sd 7:0:0:0: [sdc] 125031680 512-byte logical blocks: (64.0 GB/59.6 GiB)
2023-09-23T09:56:00.787725+02:00 manta kernel: [ 9145.638313][T27235] sd 7:0:0:0: [sdc] Write Protect is off
2023-09-23T09:56:00.787727+02:00 manta kernel: [ 9145.638320][T27235] sd 7:0:0:0: [sdc] Mode Sense: 43 00 00 00
2023-09-23T09:56:00.787728+02:00 manta kernel: [ 9145.638624][T27235] sd 7:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
2023-09-23T09:56:00.799707+02:00 manta kernel: [ 9145.647196][T27235]  sdc: sdc1 sdc2
2023-09-23T09:56:00.799725+02:00 manta kernel: [ 9145.647495][T27235] sd 7:0:0:0: [sdc] Attached SCSI removable disk
2023-09-23T09:56:01.017020+02:00 manta dbus-daemon[1176]: [system] Activating service name='org.kde.kded.smart' requested by ':1.34' (uid=1000 pid=2807 comm="/usr/bin/kded5 ") (using servicehelper)
2023-09-23T09:56:01.042388+02:00 manta dbus-daemon[1176]: [system] Successfully activated service 'org.kde.kded.smart'

# lsusb
  ...
Bus 002 Device 007: ID 0781:5575 SanDisk Corp. Cruzer Glide
  ...

# rpm -qa | grep -i virtualbox
virtualbox-kmp-default-7.0.10_k5.14.21_150500.55.7-lp155.2.5.1.x86_64
virtualbox-7.0.10-lp155.2.5.1.x86_64
virtualbox-qt-7.0.10-lp155.2.5.1.x86_64

On the guest i have:

# rpm -qa | grep -i virtualbox
virtualbox-kmp-default-7.0.10_k5.14.21_150500.55.7-lp155.2.5.1.x86_64
virtualbox-guest-tools-7.0.10-lp155.2.5.1.x86_64
virtualbox-kmp-default-7.0.8_k5.14.21_150500.53-lp155.1.6.x86_64

Likely unrelated problem i also have after the upgrade, but i’ll just mention it: KDE can not shutdown my laptop. Instead it reboots it. I can power it off with ‘systemctl poweroff’ though.

Hello,

maybe USB is deactivated for vbox as default

look at
/etc/udev/rules.d/60-vboxdrv.rules
or usr/lib/udev/rules.d/60-vboxdrv.rules

the following entries are needed for USB:

SUBSYSTEM=="usb_device", ACTION=="add", RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass}"
SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass}"
SUBSYSTEM=="usb_device", ACTION=="remove", RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor"
SUBSYSTEM=="usb", ACTION=="remove", ENV{DEVTYPE}=="usb_device", RUN+="/usr/lib/virtualbox/VBoxCreateUSBNode.sh --remove $major $minor"

greetings bmk555

Please fill a bugzilla on this. Something changed in the latest kernel to cause this.

After installing Leap 15.5 i installed virtualbox 7.0.10. After installing there came a question about activating USB-Access for vbox-Guests. Acceapting this lead to the USB-Entries in usr/lib/udev/rules.d/60-vboxdrv.rules

It work with Oracle Code on Host but not with OpenSUSE code on Host in latest kernel.

VMware also seems to have issue with newest 15.5 kernel code.

We are working to see what in our patches to make VBox work with OBS that has broken the USB attachment.

OBS is how it gets to where YAST and zypper can install it in Leap.

Some kernels are retracted, here in Leap 15.5

zypper se -s kernel-default | grep -i vr
vR | kernel-default                 | Paket      | 5.14.21-150500.55.22.1              | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
vR | kernel-default-devel           | Paket      | 5.14.21-150500.55.22.1              | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
vR | kernel-default-extra           | Paket      | 5.14.21-150500.55.22.1              | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
vR | kernel-default-optional        | Paket      | 5.14.21-150500.55.22.1              | x86_64 | Update repository with updates from SUSE Linux Enterprise 15

The Status column can contain the following values:

           i+
               installed by user request

           i
               installed automatically (by the resolver, see section Automatically installed packages)

           v
               a different version is installed

           empty
               neither of the above cases

           !
               a patch in needed state

           .l
               is shown in the 2nd column if the item is locked (see section Package Locks Management)

           .P
               is shown in the 2nd column if the item is part of a PTF (A program temporary fix which must be explicitly selected and will otherwise not be considered in dependency resolution).

           .R
               is shown in the 2nd column if the item has been retracted (see patch in section Package Types)

Delete them.

the 5.14.21-150500.55.22.1 kernel is bad use the 5.14.21-150500.55.19.1 kernel.
Something got built wrong but got past QA.

larryr is right, i was running 5.14.21-150500.55.22.1. Going back to 5.14.21-150500.55.19.1 resolved the issue.

I’ll file a bug