Another qubes-usb-proxy bug

Qube OS Version

xen_version : 4.14.5
Linux 6.1.1-1.fc32.qubes.x86_64

Installed Packages:

kernel-latest-qubes-vm.x86_64 1000:6.1.1-1.fc32.qubes
kernel-qubes-vm.x86_64 1000:5.15.74-1.fc32.qubes
kernel-qubes-vm.x86_64 1000:5.15.78-1.fc32.qubes
kernel-qubes-vm.x86_64 1000:5.15.81-1.fc32.qubes
kernel-qubes-vm.x86_64 1000:5.15.85-1.fc32.qubes
qubes-core-admin-client.noarch 4.1.27-1.fc32
qubes-core-dom0.noarch 4.1.30-1.fc32
qubes-core-dom0-linux.x86_64 4.1.23-1.fc32
qubes-core-dom0-linux-kernel-install.x86_64 4.1.23-1.fc32
qubes-core-qrexec.x86_64 4.1.20-1.fc32
qubes-core-qrexec-devel.x86_64 4.1.20-1.fc32
qubes-core-qrexec-dom0.x86_64 4.1.20-1.fc32
qubes-core-qrexec-libs.x86_64 4.1.20-1.fc32
qubes-db.x86_64 4.1.15-1.fc32
qubes-db-dom0.x86_64 4.1.15-1.fc32
qubes-db-libs.x86_64 4.1.15-1.fc32
qubes-desktop-linux-common.noarch 4.1.14-1.fc32
qubes-input-proxy.x86_64 1.0.28-1.fc32
qubes-input-proxy-receiver.x86_64 1.0.28-1.fc32
qubes-input-proxy-sender.x86_64 1.0.28-1.fc32
qubes-kernel-vm-support.x86_64 4.1.16-1.fc32 4.1.17-1.fc32
qubes-usb-proxy-dom0.noarch 1.1.2-1.fc32
qubes-utils.x86_64 4.1.16-1.fc32
qubes-utils-libs.x86_64 4.1.16-1.fc32
qubes-windows-tools.noarch 4.1.68-1

Affected component(s) or functionality

Attaching USB (network) devices

Brief summary

Cannot attach USB WiFI adapter to separate sys-net named disposable qube

To Reproduce
qvm-usb attach sys-net-fedora-37-min sys-usb:1-2
wait for 15-20 seconds
error
Expected behavior

Attaching should finished successfully

Actual behavior

Got very well known error:

Device attach failed: /usr/lib/qubes/usb-import: line 46: /sys/devices/platform/vhci_hcd/status: No such file or directoryNo unused port found! VM: "sys-net-fedora-37-min" File: "/usr/lib/qubes/usb-import" Version Control: https://github.com/QubesOS/qubes-app-linux-usb-proxy/blob/master/src/usb-import/usr/lib/qubes/usb-import: line 81: /sys/devices/platform/vhci_hcd/attach: No such file or directory/etc/qubes-rpc/qubes.USBAttach: line 14: 843 Aborted (core dumped) qrexec-client-vm "$domain" "qubes.USB+$busid" /usr/lib/qubes/usb-import "$statefile" < /dev/null > /dev/null 2> /dev/null

Additional context

My sys-net-fedora-37-min named disposable is running pvgrub2-pvh native 6.0.17-300.fc37.x86_64 kernel.
Also

[user@sys-net-fedora-37-min ~]$ rpm -qa | grep qubes-usb-proxy
qubes-usb-proxy-1.1.2-1.fc37.noarch

and

/usr/lib/modules/6.0.17-300.fc37.x86_64/kernel/drivers/usb/usbip

Tried quick fix from here, but to no avail:

[user@sys-net-fedora-37-min ~]$ sudo modprobe vhci-hcd 
modprobe: FATAL: Module vhci-hcd not found in directory /lib/modules/6.0.17-300.fc37.x86_64

and only this is found

/usr/lib/modules/6.0.17-300.fc37.x86_64/kernel/drivers/**bluetooth**/hci_vhci.ko.xz

Device cannot be attached to native kernel running qube.

Relevant documentation you’ve consulted

Here it is

Redirecting…
USB device attach failed · Issue #5997 · QubesOS/qubes-issues · GitHub
Cannot attach USB devices to newer Linux VMs using newer qubes-usb-proxy · Issue #6868 · QubesOS/qubes-issues · GitHub
cannot create /sys/devices/platform/vhci_hcd/attach: Directory nonexistent · Issue #4230 · QubesOS/qubes-issues · GitHub

And there’s still recent similar, if not the same issue from the lst month, haven’t been answered yet:

1 Like

From the description of User Support - Qubes OS Forum :

If you want to report a bug or other issue, please go here.

You need a Github (belonging to Microsoft) account for that. Not everyone agrees with their ToS. I do not.

2 Likes