Re: USB passthrough fails with 64GB drive but works fine with 8GB drive

[A Sudheer <asr7247@xxxxxxxxx>]

Hi 

I am able to mount 64GB usb drive to DomU  after changing the controller version to 3.

USB device i am using is version 3.2 Gen2 but the controller attached to DomU was version:2. So usbdev-attach failed earlier.

#sudo xl usbctrl-attach VM3 version=3 ports=6
#sudo xl usbdev-attach VM3 hostbus=3 hostaddr=2

With above commands, i am able to access usb storage in DomU.

i assume this is PVUSB method. Can someone confirm it ?

Thanks

Sudheer

On Thu, Aug 18, 2022 at 2:49 PM A Sudheer <asr7247@xxxxxxxxx> wrote:

Hi Juergen,

Attached the qemu-dm-VM3.log .

No errors are reported here.

With 64GB drive  in DomU, both "lsusb" and "lsblk" commands   lists the USB drive but dmesg shows I/O error. 

Thanks

Sudheer

On Thu, Aug 18, 2022 at 12:02 PM Juergen Gross <jgross@xxxxxxxx> wrote:

[removing xen-users to avoid crossposting]

On 18.08.22 08:18, A Sudheer wrote:
> Hi All
>
> On XEN-4.16 with Ubuntu 22.04 Dom0 and HVM-DomU, I tried to do a USB mass
> storage device passthrough to DomU.
> I followed the PVUSB method mentioned in
> https://wiki.xenproject.org/wiki/Xen_USB_Passthrough
> <https://wiki.xenproject.org/wiki/Xen_USB_Passthrough>.
>
> With 8GB sandisk pen drive, i am able to do USB passthrough to DomU.
> But with 64GB sandisk pendrive, though able to mount/umount in Dom0, not able to
> do passthrough to DomU.
> I see IO errors in dmesg  when tried to access the usb disk folder in DomU.
> Both 8GB and 64GB disks are 3.2Gen1. (Not tried with 16GB & 32GB drives).
>
> Does anyone know why 64GB usb disk passthrough fails with the below error ?
>
> Dmesg Error:
> -----------------
> [  128.333409] usb 2-1: reset high-speed USB device number 2 using ehci-pci
> [  128.502872] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR
> driverbyte=DRIVER_OK cmd_age=0s
> [  128.502881] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 7a b7 00 00 3f 00
> [  128.502883] blk_update_request: I/O error, dev sda, sector 31415 op
> 0x0:(READ) flags 0x80700 phys_seg 63 prio class 0

Do you have the related qemu log from dom0? Should be something like
/var/log/xen/qemu-dm-*.log


Juergen