Does Xen 4.7 support PVUSB?

202 views
Skip to first unread message

Albin Otterhaell

unread,
Jun 1, 2016, 7:15:09 PM6/1/16
to qubes...@googlegroups.com
I will first say that I don't know anything about how Xen works, so my
question could be wrong totally wrong. Please correct me!

According to Xen's wiki[1] "[...] support for PVUSB in xl/libxl is
introduced sinceXen 4.7, including both PVUSB device from config file
and PVUSB device hot-plug and unplug. Currently it supports USB 1.1 and
USB 2.0", does this mean that we'll be able to attach USB devices (other
than block devices, e.g. mobile phones and webcams) to qubes and still
be able to use USB keyboard and mouses?

[1] http://wiki.xenproject.org/wiki/Xen_USB_Passthrough

Marek Marczykowski-Górecki

unread,
Jun 1, 2016, 7:41:09 PM6/1/16
to Albin Otterhaell, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Yes, but not because of PVUSB support in xl.

According to that wiki, only dom0 backend is currently supported. And
our previous experience with PVUSB kernel drivers reveals it's really
unstable. Alternative they propose is to use backend in qemu process in
dom0, which is security disaster.

On the other hand, it turned out USBIP to be greatly improved over the
time and is quite useable. And it is possible to use it over any socket,
not only network, so we've connected it using Qubes RPC[2]. It will be
available in upcoming Qubes 3.2. There will be a separate announcement
about this major feature.

> [1] http://wiki.xenproject.org/wiki/Xen_USB_Passthrough

[2]
https://github.com/QubesOS/qubes-issues/issues/531#issuecomment-199329326

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXT3KNAAoJENuP0xzK19csOaoH/jOOkuiGcACO73L/2BJd/iQB
l0NTetQ0xH5tpWXbiQTyEmJPPci9Ndo/6sckLkN2+NKOq0Knh8kx+VkNwNjOj3Hr
UFZa1mDrHrljEEKB8BrvLmmTdiPsIhQBNc/6Fu0IoPySw5pehaVVjyQSOuRz5Rr1
K80EwaailwxHAptCUSNl9nV9C9oM+5dpMAV4eezcVHw83JWFTnfwxZdinQfcBZPc
rQfqSb6e3DC0pccKVxN4cIIocs1qIziwypiw49oMVgIRVFJzz1ZQ9dmEl0OQeQ6Z
k54jnWNgwp/Xo29SlaiGx7g3+86meUTuKehAw6VrGvvMl/xqYf7HlNCtadVj5wU=
=Anr/
-----END PGP SIGNATURE-----

Albin Otterhaell

unread,
Jun 2, 2016, 4:42:34 AM6/2/16
to qubes...@googlegroups.com
Marek Marczykowski-Górecki:
> On Wed, Jun 01, 2016 at 10:41:35PM +0000, Albin Otterhaell wrote:
>> I will first say that I don't know anything about how Xen works, so my
>> question could be wrong totally wrong. Please correct me!
>
>> According to Xen's wiki[1] "[...] support for PVUSB in xl/libxl is
>> introduced sinceXen 4.7, including both PVUSB device from config file
>> and PVUSB device hot-plug and unplug. Currently it supports USB 1.1 and
>> USB 2.0", does this mean that we'll be able to attach USB devices (other
>> than block devices, e.g. mobile phones and webcams) to qubes and still
>> be able to use USB keyboard and mouses?
>
> Yes, but not because of PVUSB support in xl.
>
> According to that wiki, only dom0 backend is currently supported. And
> our previous experience with PVUSB kernel drivers reveals it's really
> unstable. Alternative they propose is to use backend in qemu process in
> dom0, which is security disaster.
>
> On the other hand, it turned out USBIP to be greatly improved over the
> time and is quite useable. And it is possible to use it over any socket,
> not only network, so we've connected it using Qubes RPC[2]. It will be
> available in upcoming Qubes 3.2. There will be a separate announcement
> about this major feature.
>
>> [1] http://wiki.xenproject.org/wiki/Xen_USB_Passthrough
>
> [2]
> https://github.com/QubesOS/qubes-issues/issues/531#issuecomment-199329326
>
>

Thank you! This is a very important feature for me. Will we be able to
attach USB devices to different qubes, or is it still only a USBVM that
works?

And what's the ETA for R3.2?

Ivan

unread,
Jun 2, 2016, 9:24:42 AM6/2/16
to qubes...@googlegroups.com
Hi,
Quoting Marek from a recent post:

There are still few blockers (see github issues), but we hope to resolve
them somehow this week and have 3.2-rc1 shortly after. From this point,
final 3.2 will be probably in two months.

>
Reply all
Reply to author
Forward
0 new messages