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
I think they are two separate issues in usb-uas and usb-host
respectively. I probably should not have bring in the usb-host case here
but create another report for it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
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:
/:
I am also facing this issue.
On further probing, I found out that usb-uas in Qemu doesn't support
"SET_SEL" control command due to which windows driver "uaspstor.sys"
couldn't complete the enumeration.
It is clearly mentioned in USB 3.1 specs that uasp devices should handle
two new control
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:
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:
Also tried to "passthrough" the SCSI layer of an actual UASP drive with
scsi-block. No luck either.
** Attachment added: "xhci-block.png"
https://bugs.launchpad.net/qemu/+bug/1579306/+attachment/4657752/+files/xhci-block.png
--
You received this bug notification because you are a member of
I am using qemu-2.5.1. Here are the commands I used in the test cases:
qemu-system-x86_64 -enable-kvm -cpu host -m 2G -net none -full-screen
-drive file=disks/uas.qcow2,format=qcow2,cache=none,aio=native -drive
file=test.img,format=raw,if=none,id=test -device nec-usb-xhci -device
usb-uas -device
Also tried to "passthrough" the SCSI layer of an actual UASP drive with
scsi-block. No luck either.
** Attachment added: "xhci-block.png"
https://bugs.launchpad.net/qemu/+bug/1579306/+attachment/4657734/+files/xhci-block.png
--
You received this bug notification because you are a member of
usb-bot works fine
** Attachment added: "xhci-bot.png"
https://bugs.launchpad.net/qemu/+bug/1579306/+attachment/4657732/+files/xhci-bot.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
10 matches
Mail list logo
