Opened 18 months ago

Closed 18 months ago

#393 closed defect (fixed)

qvm-block doesn't see devices attached to UsbVMs

Reported by: joanna Owned by: marmarek
Priority: major Milestone: Release 1 Beta 3
Component: core Keywords:
Cc:

Description

I created a usbvm that has an OHCI controlled assigned. After I plugged a UDB storage device (that is correctly seen within the UsbVM as /dev/sda), it is not reported by qvm-block -l, and so cannot be used with any other VMs.

Change History (3)

comment:1 Changed 18 months ago by joanna

Additionally, when trying to manually expose USB device from my UsbVM to Dom0, by typing:

xl block-attach 0 phy:/dev/sda xvdz r usbvm

got the following in Dom0's dmesg:

[45941.048087] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
[46235.972432] XENBUS: Timeout connecting to device: device/vbd/268441856 (local state 3, remote state 1)
[46235.972438] XENBUS: Device not ready: device/vbd/268441856

comment:2 Changed 18 months ago by marmarek

  • Owner changed from joanna to marmarek
  • Status changed from new to accepted

This additional problem is most likely from not loaded frontend module in UsbVM.
But main problem is missing (really: disabled) udev rules file. This file also loads block frontend when first device detected.

comment:3 Changed 18 months ago by marmarek

  • Resolution set to fixed
  • Status changed from accepted to closed

​http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=0cab96ad6de746659f954d24296ef2056e7e0f27

Note: See TracTickets for help on using tickets.