USB disconnecting from several guests, no communication possible

[dbfl]

Hello,

my VMs (which worked until somewhen in September 2023 with USB devices on-the-fly) now can't communicate with these devices. The device (quite old Sony floppy drive, but similar problem with Prolific-based USB-RS232 converter) are recognized by VirtualBox, but soon after activation they get disconnected within less than half a second.

Attached logs are from a Windows 10-guest, but the same problem occurs at an OS/2 (arcaOS) guest. As recommended in viewtopic.php?f=35&t=82639 the USB device is connected using USB filter, but doesn't work (just
like with on-the-fly connection)

Has anyone encountered similar problems? Does anyone know a solution?

Thanks in advance
DIrk

further system information:

host: openSUSE 15.5, Linux 5.14.21-150500.55.22-default #1 SMP PREEMPT_DYNAMIC Wed Sep 6 08:41:01 UTC 2023 (1e6fbaf) x86_64 x86_64 x86_64 GNU/Linux
GuestAdditions 7.0.10

baack@Neubaackistan:~> id
uid=1127(baack) gid=100(users) Gruppen=100(users),461(vboxusers),491(cdrom)

baack@Neubaackistan:~> VBoxManage -version
7.0.10r158379


baack@Neubaackistan:~> VBoxManage list extpacks
Extension Packs: 0


baack@Neubaackistan:~> VBoxManage list usbhost
Host USB Devices:

UUID: 37c79fff-5039-41d6-aa99-c229b2e7f25c
VendorId: 0x138a (138A)
ProductId: 0x0097 (0097)
Revision: 1.100 (01100)
Port: 8
USB version/speed: 2/Full
Manufacturer: Validity Sensors, Inc.
SerialNumber: 116c88532481
Address: sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9//device:/dev/vboxusb/001/010
Current State: Available

UUID: 038289f4-f636-40fe-928d-2214db14fe4c
VendorId: 0x1199 (1199)
ProductId: 0x9079 (9079)
Revision: 0.6 (0006)
Port: 5
USB version/speed: 2/High
Manufacturer: Sierra Wireless, Incorporated
Product: Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A
SerialNumber: LF83038152021024
Address: sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6//device:/dev/vboxusb/001/003
Current State: Busy

UUID: 104adffb-f13e-4ebf-856f-7630aedcb88c
VendorId: 0x0bda (0BDA)
ProductId: 0x0316 (0316)
Revision: 2.4 (0204)
Port: 2
USB version/speed: 3/Super
Manufacturer: Generic
Product: USB3.0-CRW
SerialNumber: 20120501030900000
Address: sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3//device:/dev/vboxusb/002/003
Current State: Busy

UUID: 929d804f-6ec3-4ecf-b68b-e0906762213d
VendorId: 0x054c (054C)
ProductId: 0x002c (002C)
Revision: 5.1 (0501)
Port: 1
USB version/speed: 1/Full
Manufacturer: Sony
Product: USB Floppy Drive
Address: sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2//device:/dev/vboxusb/001/053
Current State: Busy

UUID: 3b08ef4f-e32d-45e8-bfb1-378504a5fad0
VendorId: 0x04f2 (04F2)
ProductId: 0xb5ab (B5AB)
Revision: 0.16 (0016)
Port: 7
USB version/speed: 2/High
Manufacturer: SunplusIT Inc
Product: Integrated Camera
Address: sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8//device:/dev/vboxusb/001/008
Current State: Busy

UUID: 58416325-c607-4fdd-b74d-5d03af4c0637
VendorId: 0x04d9 (04D9)
ProductId: 0x1400 (1400)
Revision: 1.67 (0167)
Port: 1
USB version/speed: 1/Low
Manufacturer: Holtek Semiconductor, Inc.
Product: PS/2 keyboard + mouse controller
Address: sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.2//device:/dev/vboxusb/001/006
Current State: Busy

UUID: 6862582c-f49c-44bd-8b81-be65530a74bb
VendorId: 0x03f0 (03F0)
ProductId: 0x094a (094A)
Revision: 1.0 (0100)
Port: 2
USB version/speed: 2/Low
Manufacturer: PixArt
Product: HP USB Optical Mouse
Address: sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3//device:/dev/vboxusb/001/009
Current State: Busy

baack@Neubaackistan:~>


baack@Neubaackistan:~> VBoxManage list usbfilters
Global USB Device Filters:

<none>



baack@Neubaackistan:~> VBoxManage showvminfo "Windows 10 Baackistan"
Name: Windows 10 Baackistan
Encryption: disabled
Groups: /
Guest OS: Windows 10 (64-bit)
UUID: 2e815caf-3cbd-4b33-85bd-5d823d248c4c
Config file: /home/baack/VirtualBox VMs/Windows 10 Baackistan/Windows 10 Baackistan.vbox
Snapshot folder: /home/baack/VirtualBox VMs/Windows 10 Baackistan/Snapshots
Log folder: /home/baack/VirtualBox VMs/Windows 10 Baackistan/Logs
Hardware UUID: 62dd0d4a-c604-493e-8a92-b1db5baba06b
Memory size: 4096MB
Page Fusion: disabled
VRAM size: 128MB
CPU exec cap: 100%
HPET: disabled
CPUProfile: host
Chipset: piix3
Firmware: BIOS
Number of CPUs: 2
PAE: disabled
Long Mode: enabled
Triple Fault Reset: disabled
APIC: enabled
X2APIC: disabled
Nested VT-x/AMD-V: disabled
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode: message and menu
Boot Device 1: Floppy
Boot Device 2: DVD
Boot Device 3: HardDisk
Boot Device 4: Not Assigned
ACPI: enabled
IOAPIC: enabled
BIOS APIC mode: APIC
Time offset: 0ms
BIOS NVRAM File: /home/baack/VirtualBox VMs/Windows 10 Baackistan/Windows 10 Baackistan.nvram
RTC: local time
Hardware Virtualization: enabled
Nested Paging: enabled
Large Pages: disabled
VT-x VPID: enabled
VT-x Unrestricted Exec.: enabled
AMD-V Virt. Vmsave/Vmload: enabled
IOMMU: None
Paravirt. Provider: Default
Effective Paravirt. Prov.: HyperV
State: powered off (since 2023-10-02T11:16:04.783000000)
Graphics Controller: VBoxSVGA
Monitor count: 1
3D Acceleration: disabled
2D Video Acceleration: disabled
Teleporter Enabled: disabled
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: disabled
Allow Tracing to Access VM: disabled
Tracing Configuration:
Autostart Enabled: disabled
Autostart Delay: 0
Default Frontend:
VM process priority: default
Storage Controllers:
#0: 'SATA', Type: IntelAhci, Instance: 0, Ports: 2 (max 30), Bootable
Port 0, Unit 0: UUID: 3f8f2bf9-a2bf-4ff1-bd29-7e428ab229a7
Location: "/home/baack/VirtualBox VMs/Windows 10 Baackistan/Windows 10 Baackistan.vdi"
Port 1, Unit 0: UUID: 3de298e1-3da5-4432-bfa2-194f2eddf648
Location: "/home/ti3/baack/VirtualBox VMs/VBoxGuestAdditions.iso"
NIC 1: MAC: 0800271331CC, Attachment: Bridged Interface 'eth0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
UART 3: disabled
UART 4: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: ALSA, Controller: HDA, Codec: STAC9221)
Audio playback: enabled
Audio capture: disabled
Clipboard Mode: Bidirectional
Drag and drop Mode: disabled
VRDE: disabled
OHCI USB: enabled
EHCI USB: enabled
xHCI USB: disabled
USB Device Filters:
Index: 0
Active: yes
Name: Sony USB Floppy Drive [0501]
VendorId: 054c
ProductId: 002c
Revision:
Manufacturer:
Product:
Remote: 0
Serial Number:
Bandwidth groups: <none>
Shared folders:

Name: 'Downloads', Host path: '/home/baack/Downloads' (machine mapping), writable, auto-mount

Recording enabled: no
Recording screens: 1
Screen 0:
Enabled: no
ID: 0
Record video: yes
Destination: File
File: /home/baack/VirtualBox VMs/Windows 10 Baackistan/Windows 10 Baackistan-screen0.webm
Options: vc_enabled=true,ac_enabled=true,ac_profile=med
Video dimensions: 1024x768
Video rate: 512kbps
Video FPS: 25fps
* Guest:
Configured memory balloon: 0MB

baack@Neubaackistan:~>

[mpack]

This unreliable USB connection sounds to me like a classic case of old and oxidized USB connector. What makes you think it's a VirtualBox problem?

I'd try squirting contact cleaner into the USB plug on the Sony drive. Wait for it to dry before use.

[dbfl]

Well, these devices work without VirtualBox, so IMHO, it's not the fault of an oxidized USB connector. Also I tried several USB-connectors of the host-PC. (But I didn't solder a new USB connector to the USB devices...) Sorry, but thanks for your advice.

[scottgus1]

You have a good USB filter, and the floppy drive is attaching/detaching in a continuous repeat cycle about every second-ish, according to the vbox.log. The VboxSVC.log shows a slew of these:

00:02:08.884572 USBPROXY USBProxyBackendLinux: Device 054c:002c (sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2//device:/dev/vboxusb/001/011) isn't accessible. giving udev a few seconds to fix this...

I'm going to gues something on the host has got or is getting in the way of Virtualbox's USB system.

Since it worked before September 2023 we have to look back to what changed in September 2023. Can you remember any host updates? AV updates (I figure Linux would need AV nowadays)? Installed Wireshark-like something that scans USB traffic? Have you tried uninstalling/purging Virtualbox and reinstalling?

[dbfl]

Meanwhile I tried several kernel versions of opensuse leap 15.5: usb-devices work until kernel with suses number 5.14.21-150500.55.19-default #1 SMP PREEMPT_DYNAMIC from Aug 8 22:15:01 UTC 2023 (9908c29) x86_64 x86_64 x86_64 GNU/Linux

but cedes to work since kernel 5.14.21-150500.55.22-default #1 SMP PREEMPT_DYNAMIC from Sep 6 08:41:01 UTC 2023 (1e6fbaf) x86_64 x86_64 x86_64 GNU/Linux

It seems to be possible to get a changelog from Aug 8th until Sept 6th. Should I upload it? But how to proceed?

[dbfl]

According to
https://forums.opensuse.org/t/since-the ... nes/169328
some persons are discussing this problem on that discussion list.