
For the guest operating system this will mean that it typically during the OS installation phase only senses that an unknown device is located in a PCI slot on the (virtual) motherboard, but it has no driver to actually use it. The paravirtualized network card does not exist as a physical NIC, but is a device “made up” entirely by VMware. The other type of virtual network adapters are the “paravirtualized”. The VMkernel has to in “real time” emulate the exact behavior of the specific Intel 82545EM or 82574 cards, which will cost time and CPU cycles. The negative side is when using the default emulated adapters extra work is needed for every frame being sent or received from the guest operating system (which could be many thousands each second). It could be used to even (if needed) install the guest operating system by PXE since the E1000 device is available already from the BIOS start up. The positive side of the emulated network adapters are that they work “out of the box” and need no external code from VMware. The E1000E needs VM hardware version 8 or later.Ībove in Windows 2008 R2 with an emulated E1000 adapter the native guest operating system device driver is in use. This card is the default when creating almost all virtual machines and is by that widely used.Į1000E – emulates a newer real network adapter, the 1 Gbit Intel 82574, and is available for Windows 2012 and later. (Note that the physical network cards in the physical ESXi host is totally unrelated.) The VMkernel will present something that to the guest operating system will look exactly as some specific real world hardware and the guest could detect them through plug and play and use a native device driver.Į1000 – which will emulate a 1 Gbit Intel 82545EM card, and is available for most operating systems since the generation of Windows Server 2003. These are virtual hardware who emulates real existing physical network adapters. The virtual adapters belong to either of two groups:

The VMware administrator has several different virtual network adapters available to attach to the virtual machines.


This article explains the difference between the virtual network adapters and part 2 will demonstrate how much network performance could be gained by selecting the paravirtualized adapter. Network performance with VMXNET3 compared to E1000E and E1000.
