User Manual

Virtual Guest Tagging (VGT) is not supported. The model explained above applies to

Virtual Switch Tagging (VST) only.

Rev 2.2-1.0.1

Mellanox Technologies

Migration

Some Hypervisors provide the ability to migrate a virtual machine from one physical server to

another, this feature is seamlessly supported by PV-EoIB. Any network connectivity over EoIB

will automatically be resumed on the new physical server. The downtime that may occur during

this process is minor.

Resources Cleanup

When a virtual interface within the Guest OS is no longer connected to an EoIB link, its MAC

address need to be removed from the EoIB driver. The cleaning is managed by the Garbage Col-

lector (GC) service. The GC functionality is included in the mlx4_vnic daemon (python script):

# /sbin/mlx4_vnicd

• To enable/disable the mlx4_vnic daemon,

a. Edit the /etc/infiniband/mlx4_vnic.conf file by including the line:

# mlx4_vnicd=<yes|no> [parameters]

b. Start the service mlx4_vnic_confd to read and apply the configuration:

# /etc/init.d/mlx4_vnic_confd start

• To see full list of the daemon parameters, run:

# mlx4_vnicd --help

For example, to enable mlx4_vnic daemon with GC:

# cat /etc/infiniband/mlx4_vnic.conf

mlx4_vnicd=yes gc_enable=yes

# /etc/init.d/mlx4_vnic_confd start

Checking configuration file: [ OK ]

Starting mlx4_vnicd (pid 30920): [ OK ]

The mlx4_vnicd daemon requires xenstore or libvirt to run.

Some Hypervisors may not have enough memory for the driver domain, as a result mlx4_vnic

driver may fail to initialize or create more vNics, causing the machine to be unresponsive.

• To avoid this behavior, you can:

a. Allocate more memory for the driver domain.

For further information on how to increase dom0_mem, please refer to:

http://support.citrix.com/article/CTX126531

b. Lower the mlx4_vnic driver memory consumption by decreasing its RX/TX rings number and

length,

For further information, please refer to Section 4.3.4.1, “Module Parameters”, on page 72.