** Summary changed:
- Passthrough of UAS devices fails with Windows (10) guests
+ [usb-host] Passthrough of UAS devices fails with Windows (10) guests
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/16
Public bug reported:
Split off from https://bugs.launchpad.net/qemu/+bug/1579306 as this is a
distinct issue.
Physical USB storage devices that support the UAS protocol do not work
correctly when passed through to Windows guests (I've only tested this
with Windows 10 x64, build 1607).
Passing th
Noted, I've created https://bugs.launchpad.net/qemu/+bug/1648726 to
track the issue with passing through physical UAS devices.
--
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 d
Just echoing Tom Yan's comment; I've tried passing through what appears
to be the very same device (if not, at least the same UAS-SATA bridge)
to a VM in its entirety.
I can confirm the same result - with an otherwise identical domain
configuration, Linux guests correctly use the UAS driver:
/:
