Everyday Virtualization

Blog archive

VMXNET3 Virtual Adapter Notes

A new vSphere feature is the VMXNET3 network interface that is available to assign to a guest VM. This is one of four options available to virtual machines at version 7 (the other three being E1000, flexible and VMXNET2 enhanced).

There are a couple of key notes to using the VMXNET3 driver. The most obvious is that the guest will appear to be using a 10 Gb/s interface. While the underlying media may not actually be 10 Gb/s, the operating system will perceive it to be. This can assist in VM-to-VM traffic on the same host and port group, and this uses CPU cycles for the local traffic in lieu of the physical Ethernet media in most situations (as does VMXNET2). What it doesn't mean is that it is 10x faster than a 1 Gb/s connection. The VMware VMXNET3 whitepaper shows the gain in performance for a test situation, available in this PDF from VMware.

It's unfortunate that this driver is not the default one for a new virtual machine. There are a few reasons for this, primarily the fault tolerant (FT) virtual machine is not supported with the VMXNET3 driver, nor is it able to be used with paravirtualized SCSI drivers (PVSCSI). Check Scott Lowe's information on this topic.

Windows Server 2008 and Linux virtual machines will benefit most from using VMXNET3 due to added support of key features such as receive-side scaling (RSS). There new features with IPv6 offloading, should you be using it. There are larger transmit and receive buffer sizes with VMXNET3, which can accommodate burst-frequent and high-throughput guest VMs.

I'm going to configure my VMs for the VMXNET3 virtual network driver. I don't have any FT-required systems, nor do I use the PVSCSI drivers.

Do you see yourself using VMXNET3? Share your comments here.

Posted by Rick Vanover on 02/16/2010 at 3:13 PM


Reader Comments:

Mon, Mar 1, 2010 Scott Ladewig Saint Louis MO

The VMXNET3 driver is compatible with PVSCSI drivers. See http://vpivot.com/2010/02/22/pvscsi-and-vmxnet3/ for rumor debunking. While FT will work with neither VMXNET3 nor PVSCSI, PVSCSI and VMXNET3 don't have any issues with each other.

Tue, Feb 23, 2010 Andy Bailey

“If one physical ESX server goes down everything migrates to another to keep running.” Nothing could be further from the truth. This is not Fault Tolerance, but sadly, a grave misconception that has been pedalled for years by enterprise virtualization providers. If the server fails, all your VM’s fail taking down all the applications and services that they are running. You have to restart them all on a spare node. Restarting=downtime. True Fault Tolerance is only possible on ultra high availability servers, such Stratus ftserver, which guarantee 99.9999% availability.

Tue, Feb 16, 2010 Rick Vanover Grand Rapids, MI

To you other point yes, you can have implied fault tolerance by assigning n > 1 physical vmnic interfaces to the virtual switch containing the port group in which the VM resides. That is something other than what I'm talking about in this piece, however.

Tue, Feb 16, 2010 Rick Vanover Grand Rapids MI

I am referring to the FT VM feature. Basically having two hosts dedicate to the CPU and RAM of a VM, and using the same shared storage. This is a new vSphere feature.

Tue, Feb 16, 2010

I am not sure what you mean by fault tolerant. Isn't the nature of virtualization to be fault tolerant? If one physical ESX server goes down everything migrates to another to keep running. What type of server apps would not be a good fit for this adapter? Exchange running NLB or SQL Clusters?

Add Your Comment:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Comment:
Please type the letters/numbers you see above