d6fb867888
Removed duplicate abbrev definitions Signed-off-by: Rafael Jardim <rafaeljordao.jardim@windriver.com> Change-Id: I7910d9f54e158250004abd7e17a4e119f8064252 Signed-off-by: Ron Stone <ronald.stone@windriver.com>
2.3 KiB
PCI SR-IOV Ethernet Interface Devices
A ethernet interface is a physical ethernet that implements hardware-based virtualization mechanisms to expose multiple virtual network interfaces that can be used by one or more virtual machines simultaneously.
The -SIG Single Root I/O Virtualization and Sharing () specification defines a standardized mechanism to create individual virtual ethernet devices from a single physical ethernet interface. For each exposed virtual ethernet device, formally referred to as a Virtual Function (VF), the interface provides separate management memory space, work queues, interrupts resources, and streams, while utilizing common resources behind the host interface. Each VF therefore has direct access to the hardware and can be considered to be an independent ethernet interface.
When compared with a Passthrough ethernet interface, a ethernet interface:
- Provides benefits similar to those of a Passthrough ethernet interface, including lower latency packet processing.
- Scales up more easily in a virtualized environment by providing multiple VFs that can be attached to multiple virtual machine interfaces.
- Shares the same limitations, including the lack of support for , , , and live migration.
- Has the same requirements regarding the configuration of the access switches.
- Provides a similar configuration workflow when used on .
The configuration of a ethernet interface is identical to Configure PCI Passthrough ethernet Interfaces
<configure-pci-passthrough-ethernet-interfaces> except
that
- you use pci-sriov instead of pci-passthrough when defining the network type of an interface
- the segmentation ID of the project network(s) used is more significant here since this identifies the particular of the interface
- when creating the neutron port, you must use
--vnic-typedirect - when creating a neutron port backed by an , you must use
--vnic-type direct