I'm running a ASRock X570 Taichi with a Gigabyte Titan Ridge AIC on Proxmox 6.1-8 with Ryzen 9 3900X. I do want to use the system as a workstation, so I followed the instructions in the wiki and installed the gnome desktop environment.
[ 2055.227299] thunderbolt 0000:05:00.0: enabling device (0000 -> 0002)
[ 2055.289185] pci 0000:15:00.0: enabling device (0000 -> 0002)
[ 2055.289331] xhci_hcd 0000:15:00.0: xHCI Host Controller
[ 2055.289334] xhci_hcd 0000:15:00.0: new USB bus registered, assigned bus number 1
[ 2055.290502] xhci_hcd 0000:15:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000200009810
[ 2055.290752] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03
[ 2055.290753] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2055.290754] usb usb1: Product: xHCI Host Controller
[ 2055.290755] usb usb1: Manufacturer: Linux 5.3.18-3-pve xhci-hcd
[ 2055.290756] usb usb1: SerialNumber: 0000:15:00.0
[ 2055.290831] hub 1-0:1.0: USB hub found
[ 2055.290838] hub 1-0:1.0: 2 ports detected
I'm having issues with the thunderbolt controller. For some reasons every few seconds a new USB bus is registered. Here is a github gist of boltctl monitor and dmesg -w. I have no clue what this is about. I would appreciate some help.
I'm also trying to get Thunderbolt (TB) working on a VM. I'm using a Gibabyte (GB) Titan Ridge PCIe card on a GB TRX40 Designare mobo (presently in the large slot farthest from CPU). First off, I'm having no trouble passing through USB, Ethernet or SATA controllers; nor problems passing GPU or NVMe SSD; the basic techniques I seem to understand.
However, I am having trouble passing through the whole TB tree. I see it broken down into 7 addresses, not the one you referenced (but this may be due to what info we each requested through Linux commands). That is, when running "lspci -nnk", I get the following (Spoiler). From this you can see that only 4b:00 and 53:00 are being passed with vfio-pci substituted for the TB kernel driver. Do you see anything similar for your TB section?
But the problem is, I can only pass through 2 of the 7 addresses (NHI and USB); without the other parts, there is no TB functionality.
If "hostpciX: 49:00.0" or "hostpciX: 4a:00" is used in the VM.config file, VM will crash, giving an error such as "vfio 0000:49:00.0: failed to open /dev/vfio/58: No such file or directory".
If the directory, /dev/vfio/ is examined, the following files are present: 13 16 30 31 33 52 53 54 56 57 63 64 66 77 vfio. These are all of the IOMMU groups for the addresses which have been passed, including the two TB sections: 63 for 4b:00, 64 for 53:00.
The IOMMU groups present on my mobo can be viewed with this command: "find /sys/kernel/iommu_groups/ -type l", the results of which are in the Spoiler below. The groups for the un-passable addresses are here: 58 for 49:00, 59 for 4a:00, 60 for 4a:01, 61 for 4a:02, and 62 for 4a:0.
These missing IOMMU groups are what seems to be leading to the error noted above, leading me to think that at least part of the problem for the inability to pass the TB device is due to Proxmox's failure to create those missing files in /dev/vfio/. (BTW, I've tried blacklisting not only Thunderbolt but pcieport, as well as running an un-binding routine on boot, both without success,)
I'd like to hear how to fix this, or what I'm doing incorrectly. (And I don't know if this is part of your problem with TB too.)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
