Create Content



Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Created on Aug 8, 2019

Introduction

This document describes how to enable PVRDMA in VMware vSphere 6

On This Page

Introduction

This document instructs how to enable PVRDMA in VMware vSphere 6.5/6.7 with Mellanox with NVIDIA ConnectX network cards. 

This guide assumes that the following software and drivers are have been pre-installed:

  • VMware ESXi 6.7 Update 2, build 13006603
  • vCenter 6.7 Update 2, build 13007421
  • Distributed Switch 6.6.0
  • ConnectX® Ethernet Driver for VMware® ESXi Server 4.17.13.1-1vmw.670.2.48.13006603 
  • CentOS 7.6

References

Components Overview

vSphere Distributed Switch

A vSphere Distributed Switch provides centralized management and monitoring of the networking configuration of all hosts that are associated with the switch. You must set up a distributed switch on a vCenter Server server system, and its settings will be propagated to all hosts that are associated with the switch.

Paravirtual RDMA (PVRDMA)

Direct Memory Access (DMA) - A device's capability to access the host memory directly, without the intervention of the CPU.

Remote Direct Memory Access (RDMA) - is the The ability of to accessing memory (read, write) on a remote machine without interrupting the CPU(s) processes on the system.

RDMA Advantages:

  • Zero-copy - Allows applications to perform data transfers without involving the network software stack. Data is sent and received directly to the buffers without being copied between the network layers.

  • Kernel bypass - Allows applications to perform data transfers directly from the user-space without the kernel's involvement.

  • CPU Offload offload - Allows applications to access a remote memory without consuming any CPU time on the remote server. The remote memory server will be read without any intervention from the remote process (or processor). Moreover, the cache of the remote CPU will not be filled with the accessed memory content.

PVRDMA Architecture


Accelerating VM Data

Solution Overview

Setup

 

Solution Logical Design


Bill of Materials

Image Modified

Solution Physical Network Wiring

 

Configuration

Network Configuration

The below table provides details of the ESXi server names and details on their network configuration:

ESXi

Server

Server

Name

IP and NICs
High-Speed Ethernet Network

Management Network

192.168.1.0

ESXi-01sl01w01esx21noneeno0: From DHCP (reserved)
ESXi-02sl01w01esx22noneeno0: From DHCP (reserved)
ESXi-03sl01w01esx23noneeno0: From DHCP (reserved)
ESXi-04sl01w01esx24noneeno0: From DHCP (reserved)

The below table provides details of the VM names and details on their network configuration:

VM

Server

Name

IP and NICs
High-Speed Ethernet Network

Management Network

192.168.1.0

VM-01pvrdma-vm01192.168.11.51eno0: From DHCP (reserved)
VM-02pvrdma-vm02192.168.11.52eno0: From DHCP (reserved)
VM-03pvrdma-vm03192.168.11.53eno0: From DHCP (reserved)
VM-04pvrdma-vm04192.168.11.54eno0: From DHCP (reserved)

ESXi Host Configuration

Check the host configurations:

  1. Enable SSH Access to ESXi server.
  2. Log into the ESXi vSphere Command-Line Interface with root permissions.
  3. Verify that the host is equipped with a Mellanox an NVIDIA adapter card:

    Code Block
    languagetext
    themeFadeToGrey
    titleESXi Console
    ~ lspci | grep Mellanox
    
    0000:02:00.0 Network controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] [vmnic2]
    0000:02:00.1 Network controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] [vmnic3]
    Info
    Note: in this case, Mellanox the NVIDIA card is using vmnic2 and vmnic3.
  4. Verify that the logical RDMA devices are currently registered on the system:

    Code Block
    languagetext
    themeFadeToGrey
    titleESXi Console
    ~ esxcli rdma device list
    Name 	 Driver 	 State 	 MTU    Speed 	   Paired Uplink 	Description
    -------	 ----------	 ------	 ----   --------   -------------	-----------------------------------
    vmrdma0	 nmlx5_rdma  Active	 1024	100 Gbps   vmnic2			MT28800 Family [ConnectX-5 MT28831]
    vmrdma1	 nmlx5_rdma  Down	 1024	0		   vmnic3			MT28800 Family [ConnectX-5 MT28831]

Deployment

Before starting with the deployment process, we need to create a vSphere Distributed Switch (vDS) must be created:

Creating a vDS

To create a new vDS:

  1. Launch the vSphere Web Client, and connect to a vCenter Server instance.
  2. On the vSphere Web Client home screen, select the vCenter object from the list on the left.
    Hover over the Distributed Switches from the Inventory Lists area, then and click on the New Distributed Switch icon (see below image):

    This will launch the New vDS creation wizard.
  3. Provide a name for the new distributed switch, and select the location within the vCenter inventory where you would like to store the new vDS   (a datacenter object or a folder). Click Next.
  4. Select the version of the vDS you would like to create:
  5. Specify Set the number of uplink ports as to 2, tick . Tick the Create a default port group box, and give  give a name to that group:
  6. Click Next to Finish.

Adding

hosts

Hosts to the vDS

.

To add an ESXi host to an existing vDS:

  1. Launch the vSphere Web Client, and connect to a vCenter Server instance.
  2. Navigate to the list of distributed switches.
  3. Select Choose the new distributed switch in from the list of objects on the right, and select Add and Manage Hosts from the Actions menu:

  4. Select the Add hosts button, and click Next:

  5. Click on the New hosts green hosts option (a green plus icon) to add an ESXi host.

    This opens the Select New Host dialog box.
  6. From the list of new hosts, tick the boxes with the names of each the ESXi host hosts you would like wish to add to the vDS.

    Click OK when you are done, and then click Next to continue.

  7. In the next screen, make sure both the Manage physical adapters and Manage VMkernel adapters boxes  checkboxes are selectedticked. Click Next to continue.

  8. Configure vmnic2 in Configure vmnic2 in each ESXi host as an Uplink 1 for vDS:
  9. Create and attach the vmkernel adapter vmk2 to vDS port group the sl01-w01-vds02-pvrdma. Click pvrdma vDS port group. Click the green plus icon, and select one of the existing networksClick OK.


    Click Next.
  10. Provide an IPv4 address and Subnet mask for the vmk2 vmkernel adaptervmk2:

  11. Click Next until the wizard is finished:



  12. Click Finish:

Configure an ESXi Host for PVRDMA

To use PVRDMA in vSphere 6.5/6.7, your environment must meet meet several configuration requirements.

To configure an ESXi host for PVRDMA, follow the below steps.

Tag a VMkernel Adapter for PVRDMA

to To tag a VMkernel adapter, select it and enable it for PVRDMA communication with by performing the following steps:

  1. In the vSphere Web Client, navigate to the host.
  2. On the Configure tab, expand the System subheading and click Advanced System Settings.
  3. Locate Net.PVRDMAvmknic and click Edit.
  4. Enter the value of the VMkernel adapter that you want to use, and click OK.

    For In this example we used vmk2, vmk2 was used.


Note

Optional: 

You can use ESXI CLI to Tag To tag a vmknic created on the DVS that and used by the VRDMA will use for TCP channel, you can use ESXI CLI by running the following command line:

Code Block
languagetext
themeFadeToGrey
titleESXi Console
esxcli system settings advanced set -o /Net/PVRDMAVmknic -s vmk2

Enable Firewall Rule for PVRDMA

To enable the firewall rule for PVRDMA in the security profile of the ESXi host:

  1. In the vSphere Web Client, navigate to the host.
  2. In the Configure tab, expand the System subheading.
  3. Go to Security Profile → Firewall(6.7) or Firewall(6.5) section and click Edit.
  4. Scroll to the pvrdma rule and tick the relevant box next to it:
  5. Click OK to finish.


Note

Optional: 

You can use ESXI CLI to enable the pvrdma firewall rule (or disable the firewall) with the following command line:

Code Block
languagetext
themeFadeToGrey
titleESXi Console
esxcli network firewall ruleset set -e true -r pvrdma



Assign PVRDMA Adapter to a Virtual Machine

To enable a virtual machine to exchange data using RDMA, you must associate the VM with a PVRDMA network adapter. To do so:

  1. Locate the VM in the vSphere Web Client.
  2. Select a data center, folder, cluster, resource pool , or a host, and click on the VMs tab.
  3. Click Virtual Machines and double-click the VMfrom the list.
  4. Power off the VM.
  5. In the Configure tab of the VM, expand the Settings subheading, and select VM Hardware.
  6. Click Edit, and select the Virtual Hardware tab in the dialog box displaying the settings.
  7. At the bottom of the window next to New device, select Network, and click Add.
  8. Expand the New Network section, and connect the VM to a distributed port group.
    For Adapter Type, select PVRDMA.
  9. Expand the Memory section, tick the box next to Reserve all guest memory (All locked).
  10. Click OK to close the dialog window.
  11. Power on the virtual machine

Configure Guest OS for PVRDMA

This step assumes a procedure to assign a PVRDMA Adapter
Warning
A prerequisite of this step is assigning a PVRDMA adapter to a Virtual Machine with CentOS 7.2 or later, and Ubuntu 18.04. 

To configure a Guest OS for PVRDMA, you need to install a PVRDMA driver. The installation process depends on the ESXi version, VM tools and Guest OS version: 

Guest OS: CentOS 7.3 and later
VM hardware version 14
ESXi v6.7
Guest OS: CentOS 7.2
VM hardware version 13
ESXi v6.5


  1. Create a VM with VM Compatibility version 14, and install CentOS version 7.3 or 3 or later.
  2. Add the PVRDMA adapter over a DVS portgroup from the vCenter.
  3. Install the InfiniBand packages, and reload the pvrdma driver with the following command line:

    Code Block
    languagetext
    themeFadeToGrey
    titleVM Console
    yum groupinstall "Infiniband Support" –y
    rmmod vmw_pvrdma
    modprobe vmw_pvrdma
    ibv_devinfo






  1. Create a VM with VM Compatibility version 13, and install CentOS 7.2.
  2. Add the PVRDMA adapter over a DVS portgroup from the vCenter.
  3. Install the InfiniBand drivers with the following command line:

    Code Block
    languagetext
    themeFadeToGrey
    titleVM Console
    yum groupinstall "Infiniband Support" –y
  4. Install the pvrdma driver:

    Code Block
    languagetext
    themeFadeToGrey
    titleVM Console
    tar xf vrdma_ib_devel.tar
    cd vrdma_ib_devel/
    make
    cp pvrdma.ko /lib/modules/3.10.0-327.el7.x86_64/extra/
    depmod –a
    modprobe pvrdma
  5. Install the vrdma lib:

    Code Block
    languagetext
    themeFadeToGrey
    titleVM Console
    cd /tmp/
    tar xf libvrdma_devel.tar
    cd libvrdma_devel/
    ./autogen.sh
    ./configure --libdir=/lib64
    make
    make install
    cp pvrdma.driver /etc/libibverbs.d/
    rmmod pvrdma
    modprobe pvrdma
    ibv_devinfo


For Guest OS: Ubuntu 18.04, VM hardware version 14, ESXi v6.7 , the vmw_pvrdma driver should already be included in 18.04. The user level libraries can be installed using:

Code Block
languagetext
themeFadeToGrey
titleVM Console
apt-get install rdma-core
reboot
Info
In case the VM Compatibility compatibility version does not match the above, you can upgrade the VM Compatibility compatibility to version 13 in ESXi 6.5, and to version 14 in Esxi 6.7.

Deployment Verification

To test the communication using PVRDMA we will use a PerftestPerftest is usedThis is a collection of tests written over uverbs intended for use as a performance micro-benchmark.

The tests may be used for hardware or software tuning, as well as for functional testing.

To install and run the benchmark:

  1. Install Perftest:

    Code Block
    languagetext
    themeFadeToGrey
    titleVM Console
    yum install git
    git clone https://github.com/linux-rdma/perftest.git
    cd perftest/
    yum install autotools-dev automake
    yum install libtool
    yum install libibverbs-devel
    ./autogen.sh
    ./configure
    make -j 8
  2. Check the network interface name:

    Code Block
    languagetext
    themeFadeToGrey
    titleVM Console
    ifconfig
    ...
    ens224f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
  3. Add Static IP configuration to the network interface. Modify /etc/sysconfig/network-scripts/ifcfg-ens224f0

    Code Block
    languagetext
    themeFadeToGrey
    titleAdd to file
    HWADDR=00:50:56:aa:65:92
    DNS1=192.168.1.21
    DOMAIN=vwd.clx
    BOOTPROTO="static"
    NAME="ens224f0"
    DEVICE="ens224f0"
    ONBOOT="yes"
    USERCTL=no
    IPADDR=192.168.11.51
    NETMASK=255.255.255.0
    PEERDNS=no
    IPV6INIT=no
    IPV6_AUTOCONF=no
    ping 192.168.11.51

Repeat steps 1-3 for the second VM.

On the first VM ("Server"), run the following:

Code Block
languagetext
themeFadeToGrey
titleVM01 "Server" Console
systemctl disable firewall
systemctl stop firewalld
systemctl disable firewalld
firewall-cmd --state
./ib_write_bw -x 0 -d vmw_pvrdma0 --report_gbits

On the second VM ("Client"), run the following:

Code Block
languagetext
themeFadeToGrey
titleVM02 "Client" Console
./ib_write_bw -x 0 -F 192.168.11.51 -d vmw_pvrdma0 --report_gbits
************************************

* Waiting for client to connect... *
************************************
-------------------------------------------------------------------------------- -------
RDMA_Write BW Test
Dual-port : OFF Device : vmw_pvrdma0
Number of qps : 1 Transport type : IB
Connection type : RC Using SRQ : OFF
CQ Moderation : 100
Mtu : 1024[B]
Link type : Ethernet
GID index : 0
Max inline data : 0[B]
rdma_cm QPs : OFF
Data ex. method : Ethernet
-------------------------------------------------------------------------------- -------
local address: LID 0000 QPN 0x0004 PSN 0xfb9486 RKey 0x000005 VAddr 0x007f68c62 a1000
GID: 254:128:00:00:00:00:00:00:02:80:86:255:254:170:101:146
remote address: LID 0000 QPN 0x0002 PSN 0xe72165 RKey 0x000003 VAddr 0x007f2ab4 361000
GID: 254:128:00:00:00:00:00:00:02:80:86:255:254:170:58:174
-------------------------------------------------------------------------------- -------
#bytes #iterations BW peak[MB/sec] BW average[MB/sec] MsgRate[Mpps]
65536  5000          90.56           90.39            0.172405
-------------------------------------------------------------------------------- -------


Done!

Authors

Include Page
SA:Boris Kovalev
SA:Boris Kovalev

Related Documents

Content by Label
showLabelsfalse
showSpacefalse
sortcreation
cqllabel in ("roce","vmware")