Comment # 5 on bug 1217492 from P

(In reply to Dario Faggioli from comment #1)
> Ok, can you show use the configuration of the VM?
> 
> Can you also try to create a new VM (assuming that the one that is having
> the problem has not been re-created, which is fine), assign a USB device to
> it, and see if it works?

I've attached the configuration as homeassistant.xml
With help from the interwebs I was able to connect the Conbee II as serial
device to the VM (you'll see evidence of that in the configuration file). That
did the trick as a workaround. So in the VM I can now use the Conbee II with a
specific serial configuration setting in HomeAssistant.

I've created a new VM with the latest release of HomeAssisant. The outcome is
roughly the same. Even though the log is no longer flooded,  an almost equal
error message is generated multiple times*. And the Conbee II cannot be used
from within the VM. I've attached this configuration file as USB_Test.xml

*)
> jan 26 13:14:49 vmhost kernel: usb 1-3: reset full-speed USB device number 3 using xhci_hcd
> jan 26 13:14:49 vmhost kernel: cdc_acm 1-3:1.0: ttyACM0: USB ACM device
> jan 26 13:14:52 vmhost kernel: usb 1-3: usbfs: process 1688 (CPU 0/KVM) did not claim interface 0 before use
> jan 26 13:14:52 vmhost kernel: usb 1-3: usbfs: process 1688 (CPU 0/KVM) did not claim interface 0 before use
> jan 26 13:14:52 vmhost kernel: usb 1-3: usbfs: process 1688 (CPU 0/KVM) did not claim interface 0 before use
> jan 26 13:14:52 vmhost kernel: usb 1-3: usbfs: process 1688 (CPU 0/KVM) did not claim interface 0 before use
> jan 26 13:14:52 vmhost kernel: usb 1-3: usbfs: process 1688 (CPU 0/KVM) did not claim interface 0 before use
> jan 26 13:14:52 vmhost kernel: usb 1-3: usbfs: process 1688 (CPU 0/KVM) did not claim interface 0 before use