Using SR-IOV functionality¶

Known limitations¶

• QoS is supported since Liberty, while it has limitations. max_burst_kbps (burst over max_kbps) is not supported. max_kbps is rounded to Mbps.

• Security Group is not supported. the agent is only working with firewall_driver = neutron.agent.firewall.NoopFirewallDriver.

• No OpenStack Dashboard integration. Users need to use CLI or API to create neutron SR-IOV ports.

• Live migration is not supported for instances with SR-IOV ports.

  Note

  ARP spoofing filtering is supported since Liberty when using sriov-agent.

Environment example¶

We recommend using Open vSwitch with VLAN as segregation. This way you can combine normal VMs without SR-IOV ports and instances with SR-IOV ports on a single neutron network.

Create Virtual Functions (Compute)¶

In this step, create the VFs for the network interface that will be used for SR-IOV. Use eth3 as PF, which is also used as the interface for Open vSwitch VLAN and has access to the private networks of all machines.

The step to create VFs differ between SR-IOV card Ethernet controller manufacturers. Currently the following manufacturers are known to work:

• Intel
• Mellanox
• QLogic

For Mellanox SR-IOV Ethernet cards see: Mellanox: HowTo Configure SR-IOV VFs

To create the VFs on Ubuntu for Intel SR-IOV Ethernet cards, do the following:

1. Make sure SR-IOV is enabled in BIOS, check for VT-d and make sure it is enabled. After enabling VT-d, enable IOMMU on Linux by adding intel_iommu=on to kernel parameters. Edit the file /etc/default/grub:

   GRUB_CMDLINE_LINUX_DEFAULT="nomdmonddf nomdmonisw intel_iommu=on
   

2. Run the following if you have added new parameters:

   # update-grub
   # reboot
   

3. On each compute node, create the VFs via the PCI SYS interface:

   # echo '7' > /sys/class/net/eth3/device/sriov_numvfs
   

   Note

   On some PCI devices, observe that when changing the amount of VFs you receive the error Device or resource busy. In this case, you first need to set sriov_numvfs to 0, then set it to your new value.

   Warning

   Alternatively, you can create VFs by passing the max_vfs to the kernel module of your network interface. However, the max_vfs parameter has been deprecated, so the PCI SYS interface is the preferred method.

   You can determine the maximum number of VFs a PF can support:

   # cat /sys/class/net/eth3/device/sriov_totalvfs
   63
   

   If the interface is down, make sure it is set to up before launching a guest, else the instance will fail to spawn:

   # ip link set eth3 up
   # ip link show eth3
   8: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
      link/ether a0:36:9f:8f:3f:b8 brd ff:ff:ff:ff:ff:ff
      vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
      vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
      vf 2 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
      vf 3 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
      vf 4 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
      vf 5 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
      vf 6 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
      vf 7 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
   

4. Now verify that the VFs have been created (Should see Virtual Function device):

   # lspci | grep Ethernet
   

5. Persist created VFs on reboot:

   # echo "echo '7' > /sys/class/net/eth3/device/sriov_numvfs" >> /etc/rc.local
   

   Note

   The suggested way of making PCI SYS settings persistent is through sysfs.conf but for unknown reason changing sysfs.conf does not have any effect on Ubuntu 14.04.

For QLogic SR-IOV Ethernet cards see: User’s Guide OpenStack Deployment with SR-IOV Configuration

Whitelist PCI devices nova-compute (Compute)¶

Tell nova-compute which pci devices are allowed to be passed through. Edit the file /etc/nova/nova.conf:

[default]
pci_passthrough_whitelist = { "devname": "eth3", "physical_network": "physnet2"}

This tells nova that all VFs belonging to eth3 are allowed to be passed through to VMs and belong to the neutron provider network physnet2. Restart nova compute with service nova-compute restart to let the changes have effect.

Alternatively the pci_passthrough_whitelist parameter also supports whitelisting by:

• PCI address: The address uses the same syntax as in lspci and an asterisk (*) can be used to match anything.

  pci_passthrough_whitelist = { "address": "[[[[<domain>]:]<bus>]:][<slot>][.[<function>]]", "physical_network": "physnet2" }
  
  # Example match any domain, bus 0a, slot 00, all function
  pci_passthrough_whitelist = { "address": "*:0a:00.*", "physical_network": "physnet2" }
  

• PCI vendor_id and product_id as displayed by the Linux utility lspci.

  pci_passthrough_whitelist = { "vendor_id": "<id>", "product_id": "<id>",
                                "physical_network": "physnet2"}
  

If the device defined by the PCI address or devname corresponds to a SR-IOV PF, all VFs under the PF will match the entry. Multiple pci_passthrough_whitelist entries per host are supported.

Configure neutron-server (Controller)¶

1. Add sriovnicswitch as mechanism driver. Edit the file /etc/neutron/plugins/ml2/ml2_conf.ini:

   mechanism_drivers = openvswitch,sriovnicswitch
   

2. Find out the vendor_id and product_id of your VFs by logging in to your compute node with VFs previously created:

   # lspci -nn | grep -i ethernet
   87:00.0 Ethernet controller [0200]: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection [8086:10f8] (rev 01)
   87:10.1 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
   87:10.3 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
   

3. Update the /etc/neutron/plugins/ml2/ml2_conf_sriov.ini on each controller. In our case the vendor_id is 8086 and the product_id is 10ed. Tell neutron the vendor_id and product_id of the VFs that are supported.

   supported_pci_vendor_devs = 8086:10ed
   

4. Add the newly configured ml2_conf_sriov.ini as parameter to the neutron-server daemon. Edit the file /etc/init/neutron-server.conf:

   --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini
   --config-file /etc/neutron/plugins/ml2/ml2_conf_sriov.ini
   

5. To make the changes have effect, restart the neutron-server service with the service neutron-server restart.

Configure nova-scheduler (Controller)¶

1. On every controller node running nova-scheduler add PCIDeviceScheduler to the scheduler_default_filters parameter and add a new line for scheduler_available_filters parameter under the [default] section in /etc/nova/nova.conf:

   [DEFAULT]
   scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter, PciPassthroughFilter
   scheduler_available_filters = nova.scheduler.filters.all_filters
   scheduler_available_filters = nova.scheduler.filters.pci_passthrough_filter.PciPassthroughFilter
   

2. Now restart the nova-scheduler service with service nova-scheduler restart.

Enable neutron sriov-agent (Compute)¶

1. On each compute node edit the file /etc/neutron/plugins/ml2/ml2_conf_sriov.ini:

   [securitygroup]
   firewall_driver = neutron.agent.firewall.NoopFirewallDriver
   
   [sriov_nic]
   physical_device_mappings = physnet2:eth3
   exclude_devices =
   

   exclude_devices is empty so all the VFs associated with eth3 may be configured by the agent. If you want to exclude specific VFs, add them to the exclude_devices parameter as follows:

   exclude_devices = eth1:0000:07:00.2; 0000:07:00.3, eth2:0000:05:00.1; 0000:05:00.2
   

2. Test whether the sriov-agent runs successfully:

   # neutron-sriov-nic-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf_sriov.ini
   

3. Enable the neutron-sriov-agent to start automatically at system start. If your distribution does not come with a daemon file for your init system, create a daemon configuration file. For example on Ubuntu install the package:

   # apt-get install neutron-plugin-sriov-agent
   

Creating instances with SR-IOV ports¶

After the configuration is done, you can now launch Instances with neutron SR-IOV ports.

1. Get the id of the neutron network where you want the SR-IOV port to be created:

   $ net_id=`neutron net-show net04 | grep "\ id\ " | awk '{ print $4 }'`
   

2. Create the SR-IOV port. We specify vnic_type direct, but other options include macvtap:

   $ port_id=`neutron port-create $net_id --name sriov_port --binding:vnic_type direct | grep "\ id\ " | awk '{ print $4 }'`
   

3. Create the VM. For the nic we specify the SR-IOV port created in step 2:

   $ nova boot --flavor m1.large --image ubuntu_14.04 --nic port-id=$port_id test-sriov