Hi, I'm trying to passthrough a peculiar USB device. My best guess on what's happening: It's not supposed to be talked to from anything but the custom, non-Linux libusb-based "driver application" and resets itself whenever it detects something that's not according to their driver - including operations that are pretty standard and no problem at all for other devices. Unfortunately, that also means that it resets itself when trying boot the guest it's supposed to be passed through. This causes the USB address on the Linux host to change (/dev/usb/01/xx becomes /dev/usb/01/xx+1), which in turn appears to prevent it from being passed through the guest correctly. I've tried both the spice-based and the other redirection method, I've tried attaching it purely based on USB vendor and product id, tested various suggestions that I could find across the internet, but I constantly run into the same problem over and over again. I've tested a number of other devices, they all work fine - it's only this one device that's acting up and I'm now out of ideas. I will appreciate any and every suggestion. Thanks, -- Stefan Cornelius / Red Hat Product Security
