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
Virtualized USB failing pyudev check #110
Comments
@brycepg, can you checkout the devel brach and test with both "All drives" checked and unchecked? |
Unfortunately Multibootusb still says that no drives were found both with the All drives checkbox unchecked / checked. |
@brycepg, please post the output of the following: $ udevadm info -q all --root /dev/xvdi; udevadm info -q all --root /dev/xvdi1 |
|
Don't rely on ID_BUS udev item when checking "All devices". Should fix mbusb#110
@brycepg, please check the devel branch after this pull request gets merged |
Thanks @alindt, the fix works great. |
fixed in a150156 |
Hello,
I'm using Qubes, a Xen distribution which runs Linux paravirtual VMs. I've passed through a my usb device with multibootusb installed however multibootusb would not even detect it unless I changed some code.
The device is this initalized as a '/dev/xvdi', which means it's a "xen virtual disk" letter i. Unfortunately, this device never gets found because it fails the check at
scripts/usb.py:109
. Specifically thedevice.get('ID_BUS')
returns None instead of"usb"
or"scsi"
. I got the device to work by changing the line to:Obiously this is a hack. But multibootusb now detects the drive, and I can boot the drive in QEMU. If I do not add the
'xvdi' in device.sys_path
, then multibootusb chokes later down the line when getting device details.Here's some other info for this device:
device.driver
also returnsNone
device.sys_path
returns"/sys/devices/cvd-51840/block/xvdi/xvdi1"
device.device_type
returns"Parition"
device.subsystem
returns"block"
stat.S_ISBLK(os.stat("/dev/xvdi1").st_mode)
returnsTrue
System:
sudo lspci -vvv
returns nothing.I'm not sure how to fix this. If you have any suggestions I'd be willing to try.
The text was updated successfully, but these errors were encountered: