If SR-IOV is not available, PCI passthrough can also be used.
Note that this means that the network interface will be owned by the VM, and cannot be used by other processes.
Similar to SR-IOV, the PCI address for the interface is needed for configuring the passthrough.
Run ls -lha /sys/class/net/<interface>/ (replace <interface> with the network interface name).
This will show a file listing that should contain an entry called device. E.g.
lrwxrwxrwx 1 root root 0 May 7 17:18 device -> ../../../0000:b2:00.0
Before proceeding, locate the MAC address of the network interface. Run ip link show <interface> (replace <interface> with the network interface to use).
The output will be similar to the below example, where the MAC address is after the 'link/ether' label.
The MAC addresses is needed for mapping the interfaces in the SSC600 SW to specific ports.
4: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether c4:00:ad:9b:3b:aa brd ff:ff:ff:ff:ff:ff
With the VM powered off. Run virsh edit ssc600-1
- Remove the existing entry for the network interface that is re-configured to use PCI passthrough.
- Add a new entry inside the <devices> XML node (replace the PCI address with the correct one for your hardware)
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0xb2' slot='0x00' function='0x0'/>
</source>
</hostdev>
- When finished, run virsh nodedev-detach pci_0000_b2_00_0 (replace the PCI address with the correct one for your hardware)
- Restart the VM virsh start ssc600-1
- Update the interface mappings on the Network configuration page in the web HMI.
<filesystem type="mount" accessmode="mapped">
<driver type="path" wrpolicy="immediate"/>
<source dir="/var/lib/libvirt/images/ptp"/>
<target dir="ptp"/>
<readonly/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x04" function="0x0"/>
</filesystem>