To pass devices as PCI-E, you will need to use q35 as the BIOS, and SeaBIOS won't work. In my AMD system, the latter is shown.Īt this point you should be able to assign PCI(e) devices to guests.

It should display that IOMMU, Directed I/O or Interrupt Remapping is enabled, depending on hardware and kernel the exact message can vary. next, add the vfio modules to /etc/modulesĪfter rebooting, you can check if IOMMU is functioning by reading driver message:.The second flag allows higher performance when using SR-IOV VFs. edit /etc/default/grub, on the line GRUB_CMDLINE_LINUX_DEFAULT, add after the flag quiet two more flags:.Here, I will follow PVE's Wiki: (e)_Passthroughįor editing conf, you can use either vi or nano to edit a text file, e.g. For reference, some Asrock's consumer boards have these setting, e.g. If you do not have these setting in the BIOS, it is highly likely your system does not support SR-IOV to begin with and little can be done. Also, you want to set ACS to enable in BIOS. You can skip some steps in case you have already performed them.įirst you want to make sure IOMMU and SR-IOV are enabled in BIOS. In the following, I assume you have a fresh installation of PVE. SR-IOV is not required but I guess it doesn't hurt to learn how it can be used so I bothered.

Then run a standalone PVE and house a router VM (ClearOS) and a few NAS/Web servers. Evidently, you will need a compatible system to begin with.įirst of all, here is my system for reference: You can set this up without even connecting to internet. In this tutorial I try to outline the essential steps to get SR-IOV up and running by enabling virtual functions (VF) on your NIC in a PVE system. I am glad if you can point out anything to improve regarding the steps. I am not an expert in Linux/KVM/Networking, so my implementation might not be the best. As I have struggled through setting up (and succeed, yay!) SR-IOV with an Intel NIC, I decide to do a little write up for myself and as a sharing.

Intel x520 t2 driver