Ubuntu 23.04 KVM - USB Passthrough not working

Sarungal

New Member
Sep 7, 2024
1
0
1
Hello!
I'm struggling with the USB passthrough of my pve 8.2.4 installation into my Ubuntu 23.04 KVM guest. Logs and configs down below.
With lsusb I find my ConBee 2 stick attached and recognized by the host. I add the usb to my guest by using the vendor/device id (also tried the full port).
The device (and any other I tried) will not show up with lsusb on my ubuntu guest.


pveversion -v:
Code:
proxmox-ve: 8.2.0 (running kernel: 6.8.12-1-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-1
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1

VM Config:
Code:
agent: 1
balloon: 0
boot: c
bootdisk: scsi0
cipassword: <redacted>
cores: 4
hotplug: disk,network,usb
ide2: local-zfs:vm-100-cloudinit,media=cdrom
ipconfig0: ip=dhcp,ip6=dhcp
machine: pc,viommu=virtio
memory: 8192
meta: creation-qemu=8.1.2,ctime=1701868313
name: theed
net0: virtio=BC:24:11:64:5F:DC,bridge=vmbr0
onboot: 1
ostype: l26
scsi0: local-zfs:vm-100-disk-0,size=105984M
scsi1: extraspace:100/vm-100-disk-0.qcow2,size=1083G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=40c7cf3f-a25a-4b24-a88c-a0a34cb719c2
sshkeys: <redacted>
unused0: extraspace:vm-100-disk-0
usb0: host=1cf1:0030
vga: serial0
vmgenid: 1b04c20b-270b-46c8-9c5a-72289cad6a46

lsusb on host:
Code:
Bus 002 Device 002: ID 174c:235c ASMedia Technology Inc. Ugreen Storage Device
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb on guest is totally empty

lshw on guest:
Code:
theed                     
    description: Computer
    product: Standard PC (i440FX + PIIX, 1996)
    vendor: QEMU
    version: pc-i440fx-9.0
    width: 64 bits
    capabilities: smbios-2.8 dmi-2.8 smp vsyscall32
    configuration: boot=normal uuid=40c7cf3f-a25a-4b24-a88c-a0a34cb719c2
  *-core
       description: Motherboard
       physical id: 0
     *-firmware
          description: BIOS
          vendor: SeaBIOS
          physical id: 0
          version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
          date: 04/01/2014
          size: 96KiB
     *-cpu
          description: CPU
          product: Common KVM processor
          vendor: Intel Corp.
          physical id: 400
          bus info: cpu@0
          version: 15.6.1
          slot: CPU 0
          size: 2GHz
          capacity: 2GHz
          width: 64 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx x86-64 constant_tsc nopl xtopology cpuid tsc_known_freq pni cx16 x2apic hypervisor lahf_lm cpuid_fault pti
          configuration: cores=4 enabledcores=4 microcode=1 threads=4
     *-memory
          description: System Memory
          physical id: 1000
          size: 8GiB
          capabilities: ecc
          configuration: errordetection=multi-bit-ecc
        *-bank
             description: DIMM RAM
             vendor: QEMU
             physical id: 0
             slot: DIMM 0
             size: 8GiB
     *-pci
          description: Host bridge
          product: 440FX - 82441FX PMC [Natoma]
          vendor: Intel Corporation
          physical id: 100
          bus info: pci@0000:00:00.0
          version: 02
          width: 32 bits
          clock: 33MHz
        *-isa
             description: ISA bridge
             product: 82371SB PIIX3 ISA [Natoma/Triton II]
             vendor: Intel Corporation
             physical id: 1
             bus info: pci@0000:00:01.0
             version: 00
             width: 32 bits
             clock: 33MHz
             capabilities: isa
             configuration: latency=0
           *-pnp00:00
                product: PnP device PNP0501
                physical id: 0
                capabilities: pnp
                configuration: driver=serial
           *-pnp00:01
                product: PnP device PNP0303
                physical id: 1
                capabilities: pnp
           *-pnp00:02
                product: PnP device PNP0f13
                physical id: 2
                capabilities: pnp
           *-pnp00:03
                product: PnP device PNP0700
                physical id: 3
                capabilities: pnp
           *-pnp00:04
                product: PnP device PNP0b00
                physical id: 4
                capabilities: pnp
        *-ide
             description: IDE interface
             product: 82371SB PIIX3 IDE [Natoma/Triton II]
             vendor: Intel Corporation
             physical id: 1.1
             bus info: pci@0000:00:01.1
             version: 00
             width: 32 bits
             clock: 33MHz
             capabilities: ide isa_compat_mode bus_master
             configuration: driver=ata_piix latency=0
             resources: irq:0 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:e0c0(size=16)
        *-usb UNCLAIMED
             description: USB controller
             product: 82371SB PIIX3 USB [Natoma/Triton II]
             vendor: Intel Corporation
             physical id: 1.2
             bus info: pci@0000:00:01.2
             version: 01
             width: 32 bits
             clock: 33MHz
             capabilities: uhci bus_master
             configuration: latency=0
             resources: ioport:e080(size=32)
        *-bridge UNCLAIMED
             description: Bridge
             product: 82371AB/EB/MB PIIX4 ACPI
             vendor: Intel Corporation
             physical id: 1.3
             bus info: pci@0000:00:01.3
             version: 03
             width: 32 bits
             clock: 33MHz
             capabilities: bridge
             configuration: latency=0
        *-generic
             description: Unclassified device
             product: Red Hat, Inc.
             vendor: Red Hat, Inc.
             physical id: 2
             bus info: pci@0000:00:02.0
             version: 01
             width: 64 bits
             clock: 33MHz
             capabilities: bus_master cap_list
             configuration: driver=virtio-pci latency=0
             resources: irq:10 memory:fea00000-fea03fff
           *-virtio0 UNCLAIMED
                description: Virtual I/O device
                physical id: 0
                bus info: virtio@0
        *-scsi
             description: SCSI storage controller
             product: Virtio SCSI
             vendor: Red Hat, Inc.
             physical id: 5
             bus info: pci@0000:00:05.0
             version: 00
             width: 64 bits
             clock: 33MHz
             capabilities: scsi msix bus_master cap_list
             configuration: driver=virtio-pci latency=0
             resources: irq:11 ioport:e000(size=64) memory:fe440000-fe440fff memory:fea04000-fea07fff
           *-virtio1 UNCLAIMED
                description: Virtual I/O device
                physical id: 0
                bus info: virtio@1
                configuration: driver=virtio_scsi
        *-communication
             description: Communication controller
             product: Virtio console
             vendor: Red Hat, Inc.
             physical id: 8
             bus info: pci@0000:00:08.0
             version: 00
             width: 64 bits
             clock: 33MHz
             capabilities: msix bus_master cap_list
             configuration: driver=virtio-pci latency=0
             resources: irq:11 ioport:e040(size=64) memory:fe441000-fe441fff memory:fea08000-fea0bfff
           *-virtio2 UNCLAIMED
                description: Virtual I/O device
                physical id: 0
                bus info: virtio@2
                configuration: driver=virtio_console
        *-network
             description: Ethernet controller
             product: Virtio network device
             vendor: Red Hat, Inc.
             physical id: 12
             bus info: pci@0000:00:12.0
             version: 00
             width: 64 bits
             clock: 33MHz
             capabilities: msix bus_master cap_list rom
             configuration: driver=virtio-pci latency=0
             resources: irq:10 ioport:e0a0(size=32) memory:fe442000-fe442fff memory:fea0c000-fea0ffff memory:fe400000-fe43ffff
           *-virtio3
                description: Ethernet interface
                physical id: 0
                bus info: virtio@3
                logical name: eth0
                serial: bc:24:11:64:5f:dc
                capabilities: ethernet physical
                configuration: autonegotiation=off broadcast=yes driver=virtio_net driverversion=1.0.0 ip=192.168.178.47 link=yes multicast=yes
        *-pci:0
             description: PCI bridge
             product: QEMU PCI-PCI bridge
             vendor: Red Hat, Inc.
             physical id: 1e
             bus info: pci@0000:00:1e.0
             version: 00
             slot: 0, chassis 1
             width: 64 bits
             clock: 66MHz
             capabilities: pci msi slotid normal_decode cap_list
             resources: memory:fe443000-fe4430ff ioport:d000(size=4096) memory:fe200000-fe3fffff ioport:fe800000(size=2097152)
           *-usb UNCLAIMED
                description: USB controller
                product: QEMU XHCI Host Controller
                vendor: Red Hat, Inc.
                physical id: 1b
                bus info: pci@0000:01:1b.0
                version: 01
                width: 64 bits
                clock: 33MHz
                capabilities: msix xhci bus_master cap_list
                configuration: latency=0
                resources: memory:fe200000-fe203fff
        *-pci:1
             description: PCI bridge
             product: QEMU PCI-PCI bridge
             vendor: Red Hat, Inc.
             physical id: 1f
             bus info: pci@0000:00:1f.0
             version: 00
             slot: 0, chassis 2
             width: 64 bits
             clock: 66MHz
             capabilities: pci msi slotid normal_decode cap_list
             resources: memory:fe444000-fe4440ff ioport:c000(size=4096) memory:fe000000-fe1fffff ioport:fe600000(size=2097152)
  *-input
       product: Power Button
       physical id: 1
       logical name: input0
       logical name: /dev/input/event0
       capabilities: platform

What made me curious is, that all usb hardware (which are printed with lshw on the guest) is stated as "unclaimed".

I don't find any errors in dmesg of the host and nothing about USB on the guest.

Am I doing something wrong? Any ideas what could be missing? Maybe something on the guest side?

I appreciate every help I can get!
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!