Comment # 7 on bug 1178275 from Gus Fos

I think this is the issue that is affecting me as well. I have a USB EV Cert
token from Sectigo, that I have mounted to a Windows 10 VM running in KVM. It
has worked flawlessly for a long time, but after I went from October 14 update
to November 19 snapshot, it has stopped working. 

This is how it is mounted to KVM and is the same config that I have run for a
year:

<hostdev mode="subsystem" type="usb" managed="yes">
  <source startupPolicy="optional">
    <vendor id="0x0529"/>
    <product id="0x0620"/>
  </source>
</hostdev>


This is what I get from dmesg when I plug in the USB and then start the VM:

[55212.993512] usb 1-2: new full-speed USB device number 15 using xhci_hcd
[55213.147159] usb 1-2: New USB device found, idVendor=0529, idProduct=0620,
bcdDevice= 0.01
[55213.147164] usb 1-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[55213.147166] usb 1-2: Product: Token JC
[55213.147169] usb 1-2: Manufacturer: SafeNet
[55289.253516] virbr0: port 1(vnet5) entered blocking state
[55289.253520] virbr0: port 1(vnet5) entered disabled state
[55289.253666] device vnet5 entered promiscuous mode
[55289.254320] virbr0: port 1(vnet5) entered blocking state
[55289.254324] virbr0: port 1(vnet5) entered listening state
[55291.269169] virbr0: port 1(vnet5) entered learning state
[55293.285164] virbr0: port 1(vnet5) entered forwarding state
[55293.285166] virbr0: topology change detected, propagating
[55294.497605] usb 1-2: reset full-speed USB device number 15 using xhci_hcd
[55295.509558] usb 1-2: reset full-speed USB device number 15 using xhci_hcd
[55296.681547] usb 1-2: reset full-speed USB device number 15 using xhci_hcd
[55297.961482] usb 1-2: reset full-speed USB device number 15 using xhci_hcd

And then Windows reports Device Manager reports it as "Unknown USB Deice
(Invalid Configuration Descriptor)" Code 43.

I have tested it directly on a Windows 10 laptop and then it works fine. Also
tested different ports and same issue on all ports, and other USB devices still
work fine on all ports, so it is not hardware related. I have also tested to
change USB controllers and different configs for the VM, but nothing helps. 

So I'm pretty sure this must be from an update during that time period that
have broken this.