Not sure if it's relevant, but when I try completely passthrough a UASP device to the VM through usb-host, only the BOT/MSC part is exposed. This is not the case when I do the same thing to a Linux guest (btw usb- uas apparently works fine in Linux guest as well).
** Attachment added: "xhci-block.png" https://bugs.launchpad.net/qemu/+bug/1579306/+attachment/4657745/+files/xhci-block.png -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579306 Title: usb-uas does not work in Windows (10) guest Status in QEMU: New Bug description: When I attach a "-device usb-uas" to a VM with Windows 10 10586, the device fail to start with the following error in the guest: "The device cannot start. (Code 10) {Operation Failed} The requested operation was unsuccessful" If the host controller is nec-usb-xhci, there will be two of the following error on the terminal of the host as well: "qemu-system-x86_64: usb_uas_handle_control: unhandled control request" If it's usb-ehci, ich9-usb-ehci1 or ich9-usb-echi2, this will not show up on the host side, but the device stil fails with the same error on the guest side. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1579306/+subscriptions
