Hello,
I am having an issue with one of my Proxmox hosts. I am unable to get a USB Bluetooth device working inside an Ubuntu 24.04 VM, running kernel
I have tried changing VM settings, such as BIOS, machine type, USB passthrough type (device vs port) and even tried PCI passthrough of the USB controller. Other USB devices such as storage devices work fine on the same VM. I have also tried changing BIOS settings on the host, which is a Supermicro A2SDV-8C-LN8F. The other Proxmox hosts that are working are also Supermicro-based, but different boards and CPUs, I don't have another identical machine to test with.
Output of
Output of
I have tried with other Realtek-based USB Bluetooth dongles, and each demonstrates the same symptoms with VMs on this Proxmox host only. I even tried with a full Ubuntu desktop VM, to eliminate the possibility of issues with the server ISO.
I did notice that on the A2SDV, the Bluetooth kernel modules were not included in the output of
I hope someone can help me!
I am having an issue with one of my Proxmox hosts. I am unable to get a USB Bluetooth device working inside an Ubuntu 24.04 VM, running kernel
6.11.0-21-generic. The same USB device works in Ubuntu VMs running the same version and kernel on other Proxmox hosts. The error that appears in the console just before dropping to the login prompt is as follows:
Code:
Apr 07 22:55:16 hostname kernel: Bluetooth: hci0: command 0xfc61 tx timeout
Apr 07 22:55:16 hostname kernel: Bluetooth: hci0: RTL: Failed to generate devcoredump
Apr 07 22:55:16 hostname kernel: Bluetooth: hci0: RTL: RTL: Read reg16 failed (-110)I have tried changing VM settings, such as BIOS, machine type, USB passthrough type (device vs port) and even tried PCI passthrough of the USB controller. Other USB devices such as storage devices work fine on the same VM. I have also tried changing BIOS settings on the host, which is a Supermicro A2SDV-8C-LN8F. The other Proxmox hosts that are working are also Supermicro-based, but different boards and CPUs, I don't have another identical machine to test with.
Output of
lsusb on the VM:
Code:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 002: ID 0bda:a728 Realtek Semiconductor Corp.
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 002: ID 0781:5595 SanDisk Corp. Ultra USB 3.0Output of
lsusb on the host:
Code:
Bus 002 Device 003: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 002 Device 004: ID 0781:5595 SanDisk Corp. Ultra USB 3.0
Bus 002 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0bda:a728 Realtek Semiconductor Corp.
Bus 001 Device 006: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 005: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 001 Device 003: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Virtual mouse/keyboard device
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubI have tried with other Realtek-based USB Bluetooth dongles, and each demonstrates the same symptoms with VMs on this Proxmox host only. I even tried with a full Ubuntu desktop VM, to eliminate the possibility of issues with the server ISO.
I did notice that on the A2SDV, the Bluetooth kernel modules were not included in the output of
lsmod | grep bt. They are however showing inside the VM and also on the other Proxmox hosts. I ran modprobe btusb and modprobe bluetooth, then restarted the VM, but this made no difference. I hope someone can help me!