- Minor
I have a USB bluetooth key (BCM20702A0 Bluetooth 4.0) passed into my VM by USB ID... Under 6.6.6 and prior, this worked fine, but starting in 6.7.0-rc3 through 6.7.0-rc5 this now seems to get a driver from the host kernel, which causes aberrant behavior on both the host and VM...
Symptoms include:
Full system reboot then boot into Win10 VM with device passed through by ID:
Device manager boots with the USB device listed, but now shows "This device can not start (Code 10), profiling not started"
First time I got this, I attempted to use WebUI to detach the device, this acted like it worked, but Windows now showed the device attached and working(???)... Re-attaching the device Win10 went back to "(Code 10)"... Detaching the device a second time removed the device from Windows entirely, but when Re-attaching a second time, the VM locked up for 2 minutes...
Performed a second full reboot and boot into Win10 VM has different behavior:
Device again shows as (Code 10) in Windows, but the host WebUI no longer shows either the USB adapter, and now seems to have removed the other USB device I was passing through (a Synaptics USB Finger Print Reader), and the only device now showing is a pair of headphones hooked to the PC to charge, even though the Windows VM does show the device attached but in (Code 10)...
I assume to fix this I would need to go down the road of disabling the USB driver for this device in the Syslinux config, but do we really want to go down the road of having devices like these having to have special rules that have to be remembered? Perhaps we can add the driver, but disable it by default? Or is there a driver like VFIO-PCI for usb devices?
I am willing to test solutions since I rarely use Bluetooth (Only noticed this problem when I went into device manager for other reasons), and will be remaining on 6.7.0-rc5 for now...
qw-diagnostics-20190223-1603.zip