Use the driverctl package to bind the vfio-pci driver to one of the cards as it allows designation by PCI bus rather than by PCI vendor ID which doesn't work with multiple cards with the same ID.
I've used this to allow one LSI HBA to be used by Proxmox and another identical HBA to be passed...
The solution I used on a test system where I was swapping/changing PCie cards and having the NIC change names was to add a udev rule to affix the name to it's MAC address:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{type}=="1", NAME="eno2"
I just upgraded my host from 7.4 to 8 and now I'm getting this same error a few minutes after boot, I assume when starting the 2 VMs (plus 11 LXCs). I did not see this error in 7.4 and I was running the optional 6.2 in that version as well.
Just another data point for this thread.
I have a Supermicro X10SDV-4C-TLN2F with Xeon CPU D-1521 running the latest Proxmox and one Windows 10 VM that I use for ~8 hours a day doing Remote Desktop, so nothing taxing. It does have a Quadro P620 GPU PCIe passed through in addition to an onboard...
I tried this out yesterday and while it did allow a Windows 10 VM to boot with an nVidia Quadro card on the latest kernel 5.15.35-3, I had the VM crash two times:
May 19 12:03:07 pve-x10sdv QEMU[24492]: KVM: entry failed, hardware error 0x80000021
May 19 12:03:07 pve-x10sdv QEMU[24492]: If...
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.