Open SaswatPadhi opened 8 months ago
Is qubes-usb-proxy installed in the sys-usb-eth (or its template)? It needs to be present on both ends of the qvm-usb connection.
Ah I see, thanks @marmarek! That was it.
I installed qubes-usb-proxy
in sys-usb-eth
and then I was getting modprobe
errors about missing usbip-host
module. So I had to install usbip
in both templates as well. And then everything worked as expected.
Shouldn't qubes-usb-proxy
depend on usbip
(in Fedora, not sure about the Debian package name)?
The instructions at https://www.qubes-os.org/doc/templates/minimal/ say:
USB qube, such as the template for
sys-usb
:qubes-usb-proxy
to provide USB devices to other Qubes andqubes-input-proxy-sender
to provide keyboard or mouse input to dom0.
So, my understanding was that it's only necessary in the USB qube, and not in the other qubes.
The "USB qubes" page (https://www.qubes-os.org/doc/usb-qubes/) doesn't say anything more about qubes-usb-proxy
requirements either.
We might want to clarify this bit in the minimal templates instructions, or elsewhere.
Thanks again!
- Shouldn't
qubes-usb-proxy
depend onusbip
(in Fedora, not sure about the Debian package name)?
Not really, usbip modules are included in the dom0-provided kernel, so if you use that, no need to install any kernel modules in the template. I'm not sure about package split in Fedora or Debian here, but the usbip modules are part of upstream kernel, and are usually enabled in various distributions.
It sounds like this boils down to a documentation issue in the end, so I'm updating this issue to be about this part:
- The instructions at https://www.qubes-os.org/doc/templates/minimal/ say:
USB qube, such as the template for
sys-usb
:qubes-usb-proxy
to provide USB devices to other Qubes andqubes-input-proxy-sender
to provide keyboard or mouse input to dom0.So, my understanding was that it's only necessary in the USB qube, and not in the other qubes. The "USB qubes" page (https://www.qubes-os.org/doc/usb-qubes/) doesn't say anything more about
qubes-usb-proxy
requirements either.We might want to clarify this bit in the minimal templates instructions, or elsewhere.
Thanks @marmarek and @andrewdavidwong.
@andrewdavidwong: We might also want to clarify what Marek mentioned about the usbip
module requirements for using qubes-usb-proxy
with in-kernel VMs (https://www.qubes-os.org/doc/managing-vm-kernels/#using-kernel-installed-in-the-vm).
Qubes OS release
R4.2
Brief summary
I'm not sure if this is an issue with Fedora 39 in general or just the minimal template, but dom0 is refusing to expose USB devices from my
sys-usb
AppVM usingfedora-39-minimal
TemplateVM, although it hasqubes-usb-proxy
installed!Steps to reproduce
In
dom0
:qvm-template install fedora-39-minimal
qvm-create --template fedora-39-minimal --label red sys-usb
In
sys-usb
asroot
user:dnf install qubes-usb-proxy qubes-input-proxy-sender
In
dom0
:qvm-usb
to list usb devicesqvm-usb a sys-usb-eth sys-usb:<X-Y>
-- replace<X-Y>
with desired deviceExpected behavior
USB device is attached from
sys-usb
to the target qube.Actual behavior
Spurious error about missing
qubes-usb-proxy
package.