Opened 4 years ago
Last modified 4 years ago
#19826 new defect
Can only attach USB Scanner 1st Time Virtual Machine started
| Reported by: | jce_vb | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.10 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
Environment: Fedora 31, kernel 5.7.11, virtualbox 6.1.12_139181, Epson V500 USB scanner. Not sure when problem started as both kernel and virtualbox have had updates over last several months and hadn't used that specific VM for over a month when problem first noticed. It is possible the Virtual Machine additions on the Win 10 VM may have been upgraded also during the last 2 months.
After a Fedora reboot, a new user login, and starting a Win10 virtual machine under VirtualBox, Devices -> USB always shows the scanner (and several other USB devices). Scanner can be checked and attached to VM and successfully used. Once the VM is shutdown, the next time it is started under the same Fedora user login session, none of the USB devices show up as either attached or available, and the scanner can't be added to the VM. If you logoff the current Linux user and login again, the USB devices can again be seen for the VirtualBox VM (via Devices -> USB) when the VB VM is started, and the scanner can be attached and used successfully. It's as if something in VB related to the USB interfaces is not getting properly handled when a VM is terminated, preventing VB from seeing USB devices after that point. But whatever pending USB status that is causing problems seems to be associated with the current Linux user session and gets cleaned up when that session is terminated and restarted.
When the VB USB devices can't be seen, it is still possible for a Windows 10 Virtual Machine running under Fedora Boxes to attach and successfully use the same USB scanner using the same scanner application, and that Boxes VM can be stopped and restarted without causing USB problems. That would suggest this is not a hardware issue with USB interface or the scanner.
This appears to be a bug introduced when the virtualbox 6.1.12_139181 package for f31 was installed on my system along with other Fedora updates on 7/22/2020. De-installing version 6.1.12 and re-installing version 6.1.10_138449 for Fedora 31 in the Oracle repository and installing the corresponding 6.1.10 extension pack appears to have eliminated the problem.