Hypervisor support

Edit online

You can use network adapter PCI functions with Linux in LPAR or DPM partition mode or as a KVM or z/VM® guest.

Working with PCI functions is similar regardless of how Linux is hosted. For example, you can configure for high availability through bonded interfaces on Linux in all environments.

Access methods for KVM or z/VM guests

For KVM or z/VM guests, you can connect to a PCI network adapter in two ways:
  1. Pass-through: The hypervisor assigns a PCI function directly to a guest, where it is used exclusively by that guest and is driven by the native Linux device driver that runs in the virtual machine. The hypervisor stack remains responsible for securely assigning and managing the PCI function. Linux in the guest accesses the PCI function in the same way as Linux that runs in PR/SM mode.
  2. Virtual networking:The host accesses the network adapter and provides one or more virtual network adapters to its guests. Guests access the network through these virtual adapters, which are implemented by the host and can use a programming interface that differs from that of the physical network adapter. For example:
    • z/VM VSWITCH: Provides virtual OSD channel devices to the z/VM guests.
    • KVM virtual networking:
      • MacVTap, Linux bridge, or Open vSwitch can be used as a foundation for virtual network interfaces (for example virtio-net devices) of KVM guests.
      • MacVTap and Linux bridge can be attached to a bonded interface.
      • For Linux bridge and Open vSwitch, the PCI functions that are used to create the bonded interface need to be in promiscuous mode.
Notes:
  • Other than OSA Express and OSH of Network Express® in hybrid mode, RoCE Express does not support z/VM VSWITCH technology.
  • Open vSwitch requires promiscuous mode and therefor can not be used with RoCE Express.