New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qvm-block doesn't see devices attached to UsbVMs #393

Closed
marmarek opened this Issue Mar 8, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 25 Dec 2011 21:07 UTC
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.

Migrated-From: https://wiki.qubes-os.org/ticket/393

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 26 Dec 2011 09:53 UTC
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:

[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](45941.048087]) XENBUS: Timeout connecting to device: device/vbd/268441856 (local state 3, remote state 1)
[46235.972438] XENBUS: Device not ready: device/vbd/268441856
Member

marmarek commented Mar 8, 2015

Comment by joanna on 26 Dec 2011 09:53 UTC
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:

[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](45941.048087]) XENBUS: Timeout connecting to device: device/vbd/268441856 (local state 3, remote state 1)
[46235.972438] XENBUS: Device not ready: device/vbd/268441856
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 26 Dec 2011 20:01 UTC
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.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 26 Dec 2011 20:01 UTC
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.

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment