Differences

This shows you the differences between two versions of the page.

--- acelab:opennebula_sr-iov_vmm_driver [2013/09/26 07:49]
dmacleod [Configuration Options]
+++ acelab:opennebula_sr-iov_vmm_driver [2021/12/09 16:42] (current)
@@ Line 1: / Line 1: @@
 ====== OpenNebula KVM SR-IOV Driver ======
-With the recent release of an OFED which supports SR-IOV on Infiniband HCAs it is now possible to use verbs from inside a VM. This VMM driver supports these Infiniband HCAs, and any other SR-IOV network device, in OpenNebula.
+With the release of an OFED which supports SR-IOV on Infiniband HCAs it is now possible to use verbs from inside a VM. This VMM driver supports these Infiniband HCAs, and any other SR-IOV network device, in OpenNebula.
 Demonstration Video:
@@ Line 22: / Line 22: @@
   - CentOS 6.4
-  - Mellanox OFED 2.0
+  - Mellanox OFED 2.0-3.0.0
   - libvirt 0.10.2
   - OpenNebula 4.2
 ===== Installation =====
@@ Line 56: / Line 55: @@
 x07 0x00 0x04
-. If using the driver is mlnx_ofed2 mode you need to specify the device and port number of the interface. To find the device ID execute:
+. If using the driver in "mlnx_ofed2" mode you need to specify the device and port number of the interface. To find the device ID execute:
     ls /sys/class/infiniband
 You will see a list of Infiniband devices "mlx4_<x>". The device ID is the <x>. To find the port ID execute:
@@ Line 87: / Line 86: @@
 |DUMMY_MAC_PREFIX|The prefix used to differentiate SR-IOV devices from virtual devices|
 |DRIVER_MODE|Either "generic" or "mlnx_ofed2". Generic mode passes IP address to VMs through dummy interfaces. Mlnx_ofed2 mode encodes IP address in VF GUIDs|
-|HPC_MODE|Either "on" or "off". HPC mode improves the performance of VMs. The host's CPU is passed through to the VM, may break migration. The memory backing for the VM is set to huge pages, [[#huge_pages|additional host configuration required]]). If a VM has as many vCPUs and the host has CPUs it is detected as a special case and the hosts NUMA architecture is passed to the VM. If a VM has as many vCPUs as a single NUMA node on the host the VM's CPUs will be pinned to a NUMA node.|
+|HPC_MODE|Either "on" or "off". HPC mode improves the performance of VMs. The host's CPU is passed through to the VM, may break migration. The memory backing for the VM is set to huge pages, [[#huge_pages|additional host configuration required]]. If a VM has as many vCPUs and the host has CPUs it is detected as a special case and the hosts NUMA architecture is passed to the VM. If a VM has as many vCPUs as a single NUMA node on the host the VM's CPUs will be pinned to a NUMA node.|
 ==== Libvirt “save” command ====
@@ Line 125: / Line 124: @@
 Enabling huge pages on KVM virtual machines will greatly improve memory performance. To enable huge pages on your VM hosts follow these instructions:
 http://www.linux-kvm.com/content/get-performance-boost-backing-your-kvm-guest-hugetlbfs
+Huge page backed VMs will be enabled if "HPC_MODE" is set "on".
 ==== Network Isolation ====
@@ Line 212: / Line 213: @@
             MASK=$(get_mask)
             GATEWAY=$(get_gateway)
-            echo "Writing"
             gen_iface_conf > /etc/sysconfig/network-scripts/ifcfg-${DEV}
           fi

wiki.chpc.ac.za

User Tools

Site Tools

Differences

Page Tools