Last week I replaced my external USB Proxmox drive for an extra internal M2 drive. I bought a XLR8 CS3030 1TB and installed a fresh Proxmox 6.2 on it. Went pretty smooth just copying the configs from my "old" setup. Anyhow everything works as expected again but as expected it didn't help with the USB problem.
Some new insight in trying to trouble shoot the USB passthrough problem on 48:00.1 / 48:00.3 while doing some tests.
Fact: We are unable to pass the USB controllers but if we only pass the BT USB everything works fine. I have noticed below error (USB passthrough) sometimes when booting Proxmox which after starting the VM always leads to a freeze / 99 error. Somehow linux is trying to initialise the LED controller and USB Audio (On 48:00.1 controller) but cannot access them...
So I tried the following: Next to BT I added the USB audio AND LED controller to my VM with:
usb0: host=05ac:828d # Bluetooth
usb1: host=26ce:01a2 # LED controller
usb2: host=26ce:0a01 # USB Audio
Booting VM is OK but reboot would hang, so this gives me more or less the same behaviour as when passing the complete controller. Next step I removed the LED controller and have been able to restart the VM a few times.
I think it may be related to going from linux to MacOs, back to linux and back to MacOs again... Also the LED and Audio are not recognised in lsusb
Bus 009 Device 002: ID 26ce:0a01
Bus 007 Device 006: ID 05ac:828d Apple, Inc.
Bus 007 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 007 Device 002: ID 26ce:01a2
Strange thing is that I disabled the LED in USB but apart from switching off the LED, the LED controller remains visible on USB. Would be nice if we could disable it at least to try if that solves the issue. I tried blocking linux from accessing it but so far not successfull. (Even with VFIO added, linux still boots with the xhci_pci kernel driver. (When starting the VM it is released and attached to vfio)