Re: USB passthrough fails with 64GB drive but works fine with 8GB drive
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 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 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 >> >
Re: USB passthrough fails with 64GB drive but works fine with 8GB drive
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 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 > qemu-dm-VM3.log Description: Binary data
Re: USB passthrough fails with 64GB drive but works fine with 8GB drive
[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 OpenPGP_0xB0DE9DD628BF132F.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
USB passthrough fails with 64GB drive but works fine with 8GB drive
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. 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 Complete dmesg log: --- [0.00] Linux version 5.15.0-25-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 (Ubuntu 5.15.0-25.25-generic 5.15.30) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=a1f59e2d-4208-42bb-90ad-f19c9608db6b ro quiet splash vt.handoff=7 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. [0.00] signal: max sigframe size: 1776 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xefffefff] usable [0.00] BIOS-e820: [mem 0xe000-0xefff] reserved [0.00] BIOS-e820: [mem 0xfc00-0xfc00afff] ACPI NVS [0.00] BIOS-e820: [mem 0xfc00b000-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00010f7f] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] DMI: Xen HVM domU, BIOS 4.16.2-pre 07/23/2022 [0.00] Hypervisor detected: Xen HVM [0.00] Xen version 4.16. [0.00] platform_pci_unplug: Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [0.00] platform_pci_unplug: Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. You might have to change the root device from /dev/hd[a-d] to /dev/xvd[a-d] in your root= kernel command line option [0.000348] HVMOP_pagetable_dying not supported [0.019897] tsc: Fast TSC calibration using PIT [0.019899] tsc: Detected 2096.153 MHz processor [0.019901] tsc: Detected 2096.060 MHz TSC [0.020426] e820: update [mem 0x-0x0fff] usable ==> reserved [0.020429] e820: remove [mem 0x000a-0x000f] usable [0.020434] last_pfn = 0x10f800 max_arch_pfn = 0x4 [0.020507] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.020726] last_pfn = 0xe max_arch_pfn = 0x4 [0.022710] found SMP MP-table at [mem 0x000f5aa0-0x000f5aaf] [0.022731] Using GB pages for direct mapping [0.022866] RAMDISK: [mem 0x309b9000-0x344d3fff] [0.022871] ACPI: Early table checksum verification disabled [0.022876] ACPI: RSDP 0x000F59F0 24 (v02 Xen ) [0.022880] ACPI: XSDT 0xFC00A660 54 (v01 XenHVM HVML ) [0.022885] ACPI: FACP 0xFC00A370 F4 (v04 XenHVM HVML ) [0.022890] ACPI: DSDT 0xFC001040 0092A3 (v02 XenHVM INTL 20200925) [0.022893] ACPI: FACS 0xFC001000 40 [0.022895] ACPI: FACS 0xFC001000 40 [0.022897] ACPI: APIC 0xFC00A470 80 (v02 XenHVM HVML ) [0.022899] ACPI: HPET 0xFC00A570 38 (v01 XenHVM HVML ) [0.022901] ACPI: WAET 0xFC00A5B0 28 (v01 XenHVM HVML 000
USB passthrough
Hi all, Sorry if I am starting a well-discussed thread again. I was reading through https://wiki.xenproject.org/wiki/Xen_USB_Passthrough and I understand that a xen_usbfront and xen_usbback.ko is needed. Where do i get these ? I see these provided for k 2.6.18 but that is way old. Is there a new version for these ? I tried this: $ sudo xl usbctrl-attach 14 type=pv version=2 ports=8 libxl: error: libxl_device.c:1103:device_backend_callback: Domain 14:unable to add device with path /local/domain/0/backend/vusb/14/1 libxl: error: libxl_device.c:1402:device_addrm_aocomplete: Domain 14:Unable to add vusb with id 1 libxl_device_usbctrl_add failed. and any attempt to usbdev-attach fails too Please help Thanks and regards Bhasker C V
