SR-IOV VF

The exact configuration depends on the environment and exactly what is needed from with it. Considerations include throughput requirements, functional separation, and resiliency model adopted.

<interface type='network'>

<mac address='52:54:00:10:01:02'/>

<source network='ens4f0-pool'/>

<vlan>

<tag id='1001'/>

</vlan>

<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>

</interface>

The example here sets up an SR-IOV device from the previously defined pool. If considered useful, the MAC address can be set to help easily identify the interface in the VM (as long as there are no conflicts within the same collision domain). Importantly, a VLAN filter has been defined: This VLAN is transparent to the VM as the tag is added/removed without any knowledge at the VM. The external connectivity to the server (likely a switch) will need to support VLAN tagging appropriately. This VLAN is used to filter the traffic sent between the PF and VF, and as such is useful to prevent unwanted traffic being flooded to all VFs and to keep the traffic logically separated.