mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-01-14 08:49:45 -05:00
Remove outdated no-PVUSB claim
There is an entire section below on how to do single-device passthrough since R3.2.
This commit is contained in:
parent
2d93078274
commit
a478ed0984
@ -152,9 +152,7 @@ USB stack is put to work to parse the data presented by the USB device in order
|
|||||||
to determine if it is a USB mass storage device, to read its configuration, etc.
|
to determine if it is a USB mass storage device, to read its configuration, etc.
|
||||||
This happens even if the drive is then assigned and mounted in another qube.
|
This happens even if the drive is then assigned and mounted in another qube.
|
||||||
|
|
||||||
To avoid this risk, it is possible to prepare and utilize a USB qube. However,
|
To avoid this risk, it is possible to prepare and utilize a USB qube.
|
||||||
Xen does not yet provide working PVUSB functionality, so only USB mass storage
|
|
||||||
devices can be passed to individual qubes.
|
|
||||||
|
|
||||||
For this reason, you may wish to avoid using a USB qube if you do not have a USB
|
For this reason, you may wish to avoid using a USB qube if you do not have a USB
|
||||||
controller free of input devices and programmable devices, although Qubes R3.1
|
controller free of input devices and programmable devices, although Qubes R3.1
|
||||||
|
Loading…
Reference in New Issue
Block a user