Intel AX211 WiFi 6E PCIe Passthrough no Bluetooth

[Vin]

Hello everybody,

I upgraded to Proxmox 8 and after that my Bluetooth disappeared.

Before I needed to enable "all functions" on the PCI device, in order to get WiFi and Bluetooth.

But now, when I do, the PCI device changes from 0000:00:14.3 to 0000:00:14.0, which unfortunately also now includes the USB controller.

Obviously this is not ideal, since this prevents me from passing USB devices to other VMs.

Is there a way to avoid this behaviour?

Spoiler: lspci

lspci -n -n -k; lsusb -v -v -t; nmcli radio all; rfkill list all
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4650] (rev 05)
Subsystem: ASRock Incorporation Device [1849:4650]
00:01.0 PCI bridge [0604]: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 [8086:460d] (rev 05)
Subsystem: ASRock Incorporation 12th Gen Core Processor PCI Express x16 Controller [1849:460d]
Kernel driver in use: pcieport
00:06.0 PCI bridge [0604]: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 [8086:464d] (rev 05)
Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:7a60] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a60]
Kernel driver in use: xhci_hcd
Kernel modules: mei_me, xhci_pci
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:7a27] (rev 11)
00:14.3 Network controller [0280]: Intel Corporation Device [8086:7a70] (rev 11)
Subsystem: Intel Corporation Device [8086:0094]
Kernel driver in use: vfio-pci
Kernel modules: iwlwifi
00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:7a4c] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a4c]
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:7a68] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a68]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Device [8086:7a62] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a62]
Kernel driver in use: ahci
Kernel modules: ahci
00:1a.0 PCI bridge [0604]: Intel Corporation Device [8086:7a48] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a48]
Kernel driver in use: pcieport
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:7a38] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a38]
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation Device [8086:7a3a] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a3a]
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:7a3c] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a3c]
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:7a04] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a04]
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:7a50] (rev 11)
Subsystem: ASRock Incorporation Device [1849:1897]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:7a23] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a23]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:7a24] (rev 11)
Subsystem: ASRock Incorporation Device [1849:7a24]
Kernel driver in use: intel-spi
Kernel modules: spi_intel_pci
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106 [GeForce RTX 3060] [10de:2503] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. GA106 [GeForce RTX 3060] [19da:4630]
Kernel driver in use: vfio-pci
Kernel modules: nvidiafb, nouveau
01:00.1 Audio device [0403]: NVIDIA Corporation GA106 High Definition Audio Controller [10de:228e] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. GA106 High Definition Audio Controller [19da:4630]
Kernel driver in use: vfio-pci
Kernel modules: snd_hda_intel
02:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology P2 NVMe PCIe SSD [c0a9:540a] (rev 01)
Subsystem: Micron/Crucial Technology P2 NVMe PCIe SSD [c0a9:5021]
Kernel driver in use: nvme
Kernel modules: nvme
03:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology P2 NVMe PCIe SSD [c0a9:540a] (rev 01)
Subsystem: Micron/Crucial Technology P2 NVMe PCIe SSD [c0a9:5021]
Kernel driver in use: nvme
Kernel modules: nvme
04:00.0 Ethernet controller [0200]: Intel Corporation 82575EB Gigabit Network Connection [8086:10a7] (rev 02)
Subsystem: Intel Corporation 82575EB Gigabit Network Connection [8086:0000]
Kernel driver in use: vfio-pci
Kernel modules: igb
04:00.1 Ethernet controller [0200]: Intel Corporation 82575EB Gigabit Network Connection [8086:10a7] (rev 02)
Subsystem: Intel Corporation 82575EB Gigabit Network Connection [8086:0000]
Kernel driver in use: igb
Kernel modules: igb
05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
Subsystem: ASRock Incorporation RTL8125 2.5GbE Controller [1849:8125]
Kernel driver in use: r8169
Kernel modules: r8169
06:00.0 Non-Volatile memory controller [0108]: Sandisk Corp Western Digital WD Black SN850X NVMe SSD [15b7:5030] (rev 01)
Subsystem: Sandisk Corp Western Digital WD Black SN850X NVMe SSD [15b7:5030]
Kernel driver in use: nvme
Kernel modules: nvme
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2
ID 1d6b:0003 Linux Foundation 3.0 root hub
/sys/bus/usb/devices/usb2 /dev/bus/usb/002/001
|__ Port 3: Dev 3, If 0, Class=Mass Storage, Driver=usbfs, 5000M
ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
/sys/bus/usb/devices/2-3 /dev/bus/usb/002/003
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/sys/bus/usb/devices/usb1 /dev/bus/usb/001/001
|__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ID 05e3:0608 Genesys Logic, Inc. Hub
/sys/bus/usb/devices/1-2 /dev/bus/usb/001/002
|__ Port 1: Dev 10, If 1, Class=CDC Data, Driver=usbfs, 12M
ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
/sys/bus/usb/devices/1-2.1 /dev/bus/usb/001/010
|__ Port 1: Dev 10, If 0, Class=Communications, Driver=usbfs, 12M
ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
/sys/bus/usb/devices/1-2.1 /dev/bus/usb/001/010
|__ Port 2: Dev 6, If 1, Class=Human Interface Device, Driver=usbfs, 12M
ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
/sys/bus/usb/devices/1-2.2 /dev/bus/usb/001/006
|__ Port 2: Dev 6, If 2, Class=Human Interface Device, Driver=usbfs, 12M
ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
/sys/bus/usb/devices/1-2.2 /dev/bus/usb/001/006
|__ Port 2: Dev 6, If 0, Class=Human Interface Device, Driver=usbfs, 12M
ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
/sys/bus/usb/devices/1-2.2 /dev/bus/usb/001/006
|__ Port 4: Dev 11, If 0, Class=Hub, Driver=hub/4p, 480M
ID 1a40:0101 Terminus Technology Inc. Hub
/sys/bus/usb/devices/1-4 /dev/bus/usb/001/011
|__ Port 3: Dev 18, If 1, Class=Audio, Driver=snd-usb-audio, 480M
ID 2b7e:a569
/sys/bus/usb/devices/1-4.3 /dev/bus/usb/001/018
|__ Port 3: Dev 18, If 2, Class=Human Interface Device, Driver=usbhid, 480M
ID 2b7e:a569
/sys/bus/usb/devices/1-4.3 /dev/bus/usb/001/018
|__ Port 3: Dev 18, If 0, Class=Audio, Driver=snd-usb-audio, 480M
ID 2b7e:a569
/sys/bus/usb/devices/1-4.3 /dev/bus/usb/001/018
|__ Port 1: Dev 12, If 2, Class=Video, Driver=usbfs, 480M
ID 2b7e:c569
/sys/bus/usb/devices/1-4.1 /dev/bus/usb/001/012
|__ Port 1: Dev 12, If 0, Class=Video, Driver=usbfs, 480M
ID 2b7e:c569
/sys/bus/usb/devices/1-4.1 /dev/bus/usb/001/012
|__ Port 1: Dev 12, If 3, Class=Video, Driver=usbfs, 480M
ID 2b7e:c569
/sys/bus/usb/devices/1-4.1 /dev/bus/usb/001/012
|__ Port 1: Dev 12, If 1, Class=Video, Driver=usbfs, 480M
ID 2b7e:c569
/sys/bus/usb/devices/1-4.1 /dev/bus/usb/001/012
|__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
ID 05e3:0608 Genesys Logic, Inc. Hub
/sys/bus/usb/devices/1-6 /dev/bus/usb/001/003
|__ Port 9: Dev 5, If 0, Class=Chip/SmartCard, Driver=usbfs, 12M
ID 1209:beee Generic
/sys/bus/usb/devices/1-9 /dev/bus/usb/001/005
|__ Port 9: Dev 5, If 1, Class=Human Interface Device, Driver=usbfs, 12M
ID 1209:beee Generic
/sys/bus/usb/devices/1-9 /dev/bus/usb/001/005
|__ Port 13: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 26ce:01a2
/sys/bus/usb/devices/1-13 /dev/bus/usb/001/007
|__ Port 14: Dev 8, If 0, Class=Wireless, Driver=btusb, 12M
ID 8087:0033 Intel Corp.
/sys/bus/usb/devices/1-14 /dev/bus/usb/001/008
|__ Port 14: Dev 8, If 1, Class=Wireless, Driver=btusb, 12M
ID 8087:0033 Intel Corp.
/sys/bus/usb/devices/1-14 /dev/bus/usb/001/008

Thank you in advance

Regards

 

[p.b]

Hi,

Are you really sure that this is related to Proxmox 8?

The Wireless LAN card is PCI and lspci shows e.g., this:

00:14.3 Network controller: Intel Corporation Alder Lake-S PCH CNVi WiFi (rev 11)

But the corresponding Bluetooth dapater is not a PCI device but USB.
If you do lsusb, you should see somthing similar to this:

Bus 001 Device 003: ID 8087:0033 Intel Corp.

The VM then needs two devices, the PCIe wireless adapter and the Bluetooth USB adapter (adjust the usb/hostpci index):

# Bluetooth
qm set <VMID> --usb0 host=8087:0033

# Wireless
qm set <VMID> -hostpci0 0000:00:14.3,pcie=1

Hope this is helpful...

 

[Vin]

Hi,

Are you really sure that this is related to Proxmox 8?

The Wireless LAN card is PCI and lspci shows e.g., this:


But the corresponding Bluetooth dapater is not a PCI device but USB.
If you do lsusb, you should see somthing similar to this:


The VM then needs two devices, the PCIe wireless adapter and the Bluetooth USB adapter (adjust the usb/hostpci index):


Hope this is helpful...

No, I wasnt sure if its Proxmox 8 related
Yet I encoutered this problem only after upgrading, before I was just passing the entire PCI device.

But thank you very much, you were right

The Bluetooth Adapter was listed relativly vague as

Bus 001 Device 009: ID 8087:0033 Intel Corp

without any describiton whatsoever.

But when I passed the USB device to my windows machine, I had bluetooth.

Thanks again!

 

[ACAltair]

Hi,

Are you really sure that this is related to Proxmox 8?

The Wireless LAN card is PCI and lspci shows e.g., this:


But the corresponding Bluetooth dapater is not a PCI device but USB.
If you do lsusb, you should see somthing similar to this:


The VM then needs two devices, the PCIe wireless adapter and the Bluetooth USB adapter (adjust the usb/hostpci index):


Hope this is helpful...

In Proxmox 7, I simplely pass pcie device and get both.
After I upgrade it to 8, the bluetooth lost.
Finally find it with your word, thx.
And it is weird after upgrade, it seems that it broken the virtio drive, all scsi disk and virio nic went down.
But the drive broken after many times host reboot with normal procedure, it worked well before then.
It was fixed by run upgrade another time...

 

[leesteken]

Before I needed to enable "all functions" on the PCI device, in order to get WiFi and Bluetooth.

But now, when I do, the PCI device changes from 0000:00:14.3 to 0000:00:14.0, which unfortunately also now includes the USB controller.

Usually, the Bluetooth part of such a WiFi device is connected via USB. I find it likely that your Bluetooth is not only connected via USB but also connected to the USB controller you mentioned. If you select 'All functions' then the USB controller comes with and therefore also the Bluetooth.. Try using USB passthrough instead.
Note that if you passthrough the whole USB controller to another VM, the Bluetooth will move with it unfortunately. But you could try USB passthrough other ports of the USB controller to other VMs.

 

[v95klima]

I have the same problem on a Broadcom BCM4360ng, mounted on a PCIe card.
I used to be able to just pass through the PCIe card in its entirety and Bluetooth would be brought in automatically.
The bluetooth is listed but is not given an address, and can therefore not be used.

Assigning bluetooth in addition as separate USB does not solve the problem.

 

[Vin]

I have the same problem on a Broadcom BCM4360ng, mounted on a PCIe card.
I used to be able to just pass through the PCIe card in its entirety and Bluetooth would be brought in automatically.
The bluetooth is listed but is not given an address, and can therefore not be used.

Assigning bluetooth in addition as separate USB does not solve the problem.

check following command in the CLI, it shows you the devices the hypervisor sees

lspci -n -n -k; lsusb -v -v -t; nmcli radio all; rfkill list all