qvm-usb not functioning

Drew White

unread,

Sep 13, 2017, 9:35:46 PM9/13/17

to qubes-users

hi folks,

I try to do a qvm-usb attachment to pass a usb device through, but it doesn't let me, it tells me it fails but provides no description of error.

Is there a way to find out the errors and have them display when there is an error please?

Marke50

unread,

Sep 15, 2017, 9:39:53 AM9/15/17

to qubes-users

There should be better instructions and documentation on this and working with hardware within the vm's

P R

unread,

Sep 15, 2017, 3:11:47 PM9/15/17

to Drew White, qubes-users

Hello Drew,

Am 14.09.2017 3:35 vorm. schrieb "Drew White" <drew....@gmail.com>:

I try to do a qvm-usb attachment to pass a usb device through, but it doesn't let me, it tells me it fails but provides no description of error.

Can you provide more information:

- which Qubes Version?

- Laptop / Mainboard Modell

- Kind of USB VM (the stock USB VM?)

- if you attach USB devices, do they appear in sys-usb?

- (...)

- what kind of USB device are you trying to attach?

- to which AppVM/Operating System are you attaching it to?

- have you followed the docs at https://www.qubes-os.org/doc/usb/

more information first, answers will come second ;-)

- PhR

Drew White

unread,

Sep 18, 2017, 10:35:32 PM9/18/17

to qubes-users

On Saturday, 16 September 2017 05:11:47 UTC+10, P R wrote:
> Hello Drew,
Hi P R,

> Can you provide more information:

Yes I can.

> - which Qubes Version?
Qubes 3.2
Linux dom0 4.9.45-21.pvops.qubes.x86_64 #1 SMP Tue Aug 29 14:21:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

> - Laptop / Mainboard Modell

I have a Dell T5500
and an HP EliteBook 8460p

> - Kind of USB VM (the stock USB VM?)

Whatever VM I use. Windows or Linux. Tools or not.

> - if you attach USB devices, do they appear in sys-usb?

I have no SYS USB, they appear in Qubes since sys-usb does not work in Qubes and is still flawed and doesn't work.

> - (...)
(...) ???

> - what kind of USB device are you trying to attach?

Printer, Drive Bay, Wireless Adaptor, 3G Dongle, USB-Ethernet, and more.

> - to which AppVM/Operating System are you attaching it to?

Whatever VM I use. Windows or Linux. Tools or not.

> - have you followed the docs at https://www.qubes-os.org/doc/usb/

I'm not using a USB Qube OR a sys-usb system, I am tryign to attach a USB device from Dom0 to a guest.

> more information first, answers will come second ;-)

Is that enough information?

> - PhR
- Drew

Drew White

unread,

Sep 18, 2017, 10:36:18 PM9/18/17

to qubes-users

On Friday, 15 September 2017 23:39:53 UTC+10, Marke50 wrote:
> There should be better instructions and documentation on this and working with hardware within the vm's

I agree with you. But they do not really have decent documentation for Qubes anywhere.

You ahve to get the basics then experiment.

Drew White

unread,

Sep 18, 2017, 11:06:18 PM9/18/17

to qubes-users

Example...
Attaching the Label Printer to a Windows 7 Guest..
----------------
[{username}@dom0 Desktop]$ qvm-usb
dom0:4-1.2 04f9:2015 Brother_QL-500_K6G113252
[{username}@dom0 Desktop]$ qvm-usb --help
Usage: qvm-usb -l [options]
usage: qvm-usb -a [options] <vm-name> <device-vm-name>:<device>
usage: qvm-usb -d [options] <device-vm-name>:<device>
List/set VM USB devices.

Options:
-h, --help show this help message and exit
-l, --list
-a, --attach
-d, --detach
--no-auto-detach Fail when device already connected to other VM
--force-root Force to run, even with root privileges
[{username}@dom0 Desktop]$ qvm-usb -a win7-labeller dom0:4-1.2
ERROR: Device attach failed:
[{username}@dom0 Desktop]$
----------------

When I had things attached to a sys-usb, the sys-usb kept losing things.
It kept saying it had them then a moment later it powered the usb device down.
Or else it just forgot it was there.
Or never told Dom0 that it had the device.

Marke50

unread,

Sep 18, 2017, 11:08:03 PM9/18/17

to qubes-users

https://www.qubes-os.org/doc/usb/
Scroll to the bottom until you find "How to attach USB drives"

I just tried this today and it worked well

Drew White

unread,

Sep 19, 2017, 2:09:35 AM9/19/17

to qubes-users

Attaching as a BLOCK DEVICE works fine. it's not qvm-block that I am having issues with.

Thanks for trying.

Drew White

unread,

Sep 20, 2017, 1:43:50 AM9/20/17

to qubes-users

More details....
It now comes up with this...
------------------------------------------------------------

[{username}@dom0 Desktop]$ qvm-usb

Invalid 1-1_4_3 device desc in VM 'dom0'

dom0:4-1.2 04f9:2015 Brother_QL-500_K6G113252

[{username}@dom0 Desktop]$ qvm-usb -a {guestname} dom0:4-1.2
Invalid 1-1_4_3 device desc in VM 'dom0'

Foppe de Haan

unread,

Sep 20, 2017, 4:13:26 AM9/20/17

to qubes-users

Ran into this a couple of months ago. Rafael Susewind's fix:
start the template for sys-usb, or in dom0: edit /usr/lib/qubes/udev-usb-add-change and add

ID_SERIAL=`echo ${ID_SERIAL} | iconv -t ASCII//TRANSLIT`

immediately before

DESC="${ID_VENDOR_ID}:${ID_MODEL_ID} ${ID_SERIAL}"

should work. :)

Sven Semmler

unread,

Sep 20, 2017, 10:53:49 AM9/20/17

to qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09/13/2017 08:35 PM, Drew White wrote:
> I try to do a qvm-usb attachment to pass a usb device through, but
> it doesn't let me, it tells me it fails but provides no description
> of error.

Hi Drew,

are you assigning the USB device to an AppVM based on a Qubes Fedora
or Debian template? Or is it a HVM (e.g. Windows)?

/Sven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZwoD2AAoJENpuFnuPVB+262sQALfyMMKOUXFRi8Nt9tXEcxnY
F2ypVAVbe6SNQkA9GWtov43pGYvgXVBSCX0fnBQ5wRD0klKqxyygXI7co/ZBXdJC
Greq9HdNr1reunnBdgD3RmCSQzpbUppOqqzBHpC8VJz7Y5/utmspg/QwGcJzBZM7
wuPRDwNiyrC+8i0wZjLa/hFoSpGtd6uVZrAS1bQ7dS/v9jwB4nKRrak6LdhY8OR7
LJbjAE3Rri9fPV0WjoCtihx+QCrB1CZrxamDQx4YgD79FDhFlCj8K+2+y3cPJYyM
fxzXN30uXZ0s/kac9D9vVHKJX15YrVPOVewP88yRAojvfqyivzgaii2nbYlreCcw
61DNVAUcq2tanoYZbtz9xAJa8nMiaPxllq7s1639pJF4TzQj5UAEl7mA7koGt7Xw
WXfaV1ePDWotVBZdL1BFbZzu0VUXQeUg/A+oglxYlqRDSeBnRtSvEBBwYc6sK+L1
9W19UTnfXdlIviYzjJHp13C1r6u+3uB+yuKaY8iUo2QvOrYVTZ8qzaJBWHy4ViFQ
HLBET3hzE8mAb3rTHV9yl+UYWV7+kj/hj0bjaPAOjdCGFJMYu9Sc3R5PVz5VGImn
U14my9Vx5m4q65gl4QdgpYmQflLwMVUpr0hhx3rhrQKM6cdPtiXwZmmQHPSkuJvY
Gs9jnEDvmloIJB7tWzEb
=hQkV
-----END PGP SIGNATURE-----

Sven Semmler

unread,

Sep 20, 2017, 10:56:07 AM9/20/17

to qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09/20/2017 09:53 AM, Sven Semmler wrote:
> are you assigning the USB device to an AppVM based on a Qubes
> Fedora or Debian template? Or is it a HVM (e.g. Windows)?

Sorry. Ignore me. I hadn't read the whole thread.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZwoGCAAoJENpuFnuPVB+2Fx8QAN00NE1iPulTsvFxdH62pi0k
tvGdTl90N6b/QJxjPmzw6xfai19a47OvRh15gUosFze6d5HtJaej9vQYQrFsAUBc
GAIqsV5D5eDWWOhw/obMnYxGDUaqA25bmW63FSskLCXY+2+729q8WGB+HYH0Ve6o
aznAyLwuomgSR0RvoiDZ0o77hjguCIpMPZ7gcM69Mr8//FR7XdBNVi/nTSOQsLW6
xPyta+Op/TjFPcPqefMTgV6byu/w/cJKt+/9+gRum9s1rJBZObZsGlygkPIpXO/K
IbB1PN+yjF5gndxFFB301QlAgBErCdmLB0FsGwYfCAUGW0B72QngM76g9qJgUBPR
Wbj5i3K7AmV+N6CJh0Dl4aiKt/AKzc0qI+uIv9PjCK3RSUfNRIJT642sQPCIRJGi
EJI6E/oLSargxmQWiV5KwK20SlJirPj58p7AV1D+az0VWJD1MmkjVI1PYVD+4vBI
wtxIvLF7w4SBv26pEl40KDbLg6RP3K2pU99d088konmyuTSVLUiqPIlv+b5La2mo
MEuIWQ598/r/f0KxNcYpHpelVTD2xZVvV6nF5+YGAFeejDZTeAqd1Rj9vgRXsXgo
FmybmmCD3zIMHQn4xqFdjlNgz3/XRh0fCkwWFhrLNQF3LiWROEZZP2DjzHnBiRCb
e/RwqTf/LLzRo89f/Cfj
=GGW1
-----END PGP SIGNATURE-----

Drew White

unread,

Nov 19, 2017, 9:32:17 PM11/19/17

to qubes-users

Hi folks, sys-usb still isn't functioning and allowing me to attach a device.

help pleeeeease?

awokd

unread,

Nov 20, 2017, 2:45:02 PM11/20/17

to Drew White, qubes-users

Managed to find your thread from a couple months ago. What happened when
you tried Foppe's suggestion of:

Drew White

unread,

Dec 1, 2017, 12:50:21 AM12/1/17

to qubes-users

when I added his resolution, no change.

awokd

unread,

Dec 1, 2017, 6:58:59 AM12/1/17

to Drew White, qubes-users

On Fri, December 1, 2017 05:50, Drew White wrote:
> On Tuesday, 21 November 2017 06:45:02 UTC+11, awokd wrote:
>> On Mon, November 20, 2017 02:32, Drew White wrote:
>> > Hi folks, sys-usb still isn't functioning and allowing me to attach a
>> > device.
>> >
>> > help pleeeeease?

Let's start over. Describe your Qubes version, the USB device you are
trying to attach, which USB controllers you have assigned to sys-usb or
dom0, and the output of commands you use when attaching.

Zbigniew Łukasiak

unread,

Mar 22, 2019, 9:32:08 AM3/22/19

to qubes-users

I have a similar problem - qvm-usb retuns an empty list.

[root@dom0 zby]# qvm-usb
BACKEND:DEVID DESCRIPTION USED BY
[root@dom0 zby]# lsusb
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 011: ID 148f:761a Ralink Technology, Corp.
Bus 001 Device 004: ID 03f0:0641 Hewlett-Packard
Bus 001 Device 003: ID 413c:2111 Dell Computer Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This is Qubes 4.0

I tried the recoding suggestion - I added "ID_SERIAL=`echo ${ID_SERIAL} | iconv -t ASCII//TRANSLIT`" in /usr/lib/qubes/udev-usb-add-change and then removed and put back the device - but that did not change the result.

Cheers,
Zbigniew

unman

unread,

Mar 22, 2019, 10:23:49 PM3/22/19

to qubes-users

What's the USB device you are trying to attach?
I'm assuming you chose not to create a sys-usb.

Zbigniew Łukasiak

unread,

Mar 23, 2019, 5:13:06 AM3/23/19

to unman, qubes-users

This time I needed the wifi card (Ralink) - but this is not the first
time I had this problem.

> I'm assuming you chose not to create a sys-usb.

Yes - and after someone on irc advised me to create it - that fixed
the problem. Maybe this is a documentation problem - apparently
sys-usb is kind of obligatory now.

Cheers,
Zbigniew

Reply all

Reply to author

Forward