[Bug 1858319] Re: libvirt usb 3.1

2020-03-07 Thread Launchpad Bug Tracker
[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvirt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/185831

[Bug 1858319] Re: libvirt usb 3.1

2020-01-06 Thread Christian Ehrhardt 
Interesting, so it really isn't an apparmor deny as I first thought. It seems to reset the device a lot and then give up after a while. You are using 19.10 already, that should clearly be new enough for 3.1 support. Unfortunately I have no 3.1 device nor a Hub (only 3.0 devs around me) to test

[Bug 1858319] Re: libvirt usb 3.1

2020-01-06 Thread Radek Secka
Thank you for your response. I've tested all USB 3.1 ports and there is the same problem everywhere. Passthrough of the device works just fine on any USB 3.0 port. dmesg -w (USB 3.1) .. (same as USB 3.0 here ) .. [ 1200.920167] sd 8:0:0:0: [sdf] Synchronizing SCSI cache [ 1201.181831] sd 8:0:0:0:

[Bug 1858319] Re: libvirt usb 3.1

2020-01-06 Thread Christian Ehrhardt 
Hi thanks for the good quality bug report! The speed mismatch is only a warning and shows that it fails to detect the speed. The actual issue that breaks your case is the "failed to open host usb device 2:6". I'd first of all assume it might be an apparmor deny or something similar. Could you tr