Types of Virtual Network Adapters in VMware vSphere
Compare VMware vSphere virtual NIC types, including Flexible, E1000, E1000E, VMXNET2, and VMXNET3, and choose the right adapter for compatibility and performance.
A virtual network adapter, or vNIC, is the network device presented by the hypervisor to a virtual machine. The guest operating system detects and configures the vNIC much like it would configure a physical network interface.
In VMware vSphere, the adapter type affects driver availability, throughput, CPU overhead, network offloads, multiqueue support, and compatibility with virtual machine features. The best choice depends first on guest operating system support and then on performance requirements.
What a Virtual Network Adapter Does
The vNIC connects the guest operating system to a vSphere port group through the virtual switch. The guest sends and receives Ethernet traffic through this device, while ESXi and the virtual switching layer forward that traffic to other virtual machines or to a physical uplink.
Emulated and paravirtualized NICs
An emulated NIC imitates a recognizable physical network card. For example, E1000 imitates an Intel 82545EM adapter. Because many operating systems already include drivers for familiar Intel or AMD hardware, an emulated NIC can work without a virtualization-specific driver.
A paravirtualized NIC is designed specifically for a virtual machine and uses a hypervisor-aware guest driver. It avoids much of the work required to imitate physical hardware. This can reduce CPU overhead and improve throughput, offload support, and parallel packet processing. VMXNET3 is VMware's principal high-performance paravirtualized adapter.
Adapter selection alone does not guarantee performance. Results also depend on the guest driver, vSwitch or distributed switch configuration, port group and VLAN, physical uplinks, host and guest CPU resources, MTU settings, and the behavior of the workload.
Where to Select the Adapter Type
The virtual NIC type can be selected while creating a virtual machine. It can also be reviewed in the VM's virtual hardware settings and, where supported, changed while the VM is powered off.
- Open the VM's virtual hardware configuration.
- Locate the Network Adapter device.
- Review the adapter type and the connected port group or distributed port group.
- Choose the required adapter type when creating the VM or editing compatible powered-off hardware.
- Confirm that Connected and, when appropriate, Connect at power on are enabled.
Always validate guest-driver availability before changing the type. A replacement vNIC can be detected as a new network device. The guest may assign it a new interface name, while the old IP configuration remains associated with the previous interface.
VMware Virtual Network Adapter Types
Flexible
Flexible is a compatibility-oriented legacy adapter. Its initial guest-visible identity is Vlance, which emulates an AMD 79C970 PCnet32 LANCE 10 Mbps NIC.
When VMware Tools is installed, Flexible can operate using the higher-performance vmxnet driver behavior. This made it useful for older 32-bit guest operating systems whose built-in drivers recognized the legacy PCnet32/LANCE device but did not have newer VMware drivers.
Flexible is generally not the preferred choice for modern workloads. Its main value is legacy compatibility, not maximum throughput or current virtualization-aware functionality.
E1000
E1000 is an emulated Intel 82545EM Gigabit Ethernet adapter. It is widely recognized because many operating systems include an Intel-compatible driver.
Historically, E1000 was useful for systems such as Windows XP and Linux distributions using kernel 2.4.19 or later. It also served as a default adapter type for some 64-bit guest operating systems.
Its advantage is reliable guest compatibility. Its disadvantage is emulation overhead: the hypervisor must present behavior corresponding to a physical Intel device, which can consume more processing resources than a paravirtualized adapter.
E1000E
E1000E is an emulated Intel 82574L Gigabit Ethernet adapter. It is appropriate for guest operating systems that support the Intel e1000e driver family. Windows 8 and newer are examples of a compatibility category for which E1000E may be suitable.
E1000 and E1000E are both emulated Gigabit adapters, but they represent different Intel hardware models and therefore have different driver expectations. E1000E is normally selected for guest compatibility rather than maximum virtual-network performance.
VMXNET2 or Enhanced VMXNET
VMXNET2 is an enhanced version of the vmxnet family. It is virtualization-aware and provides capabilities beyond basic legacy vmxnet behavior, including jumbo-frame and hardware-offload support.
VMXNET2 was a performance-focused option for supported older environments. It has largely been superseded by VMXNET3, so it is normally reserved for legacy or specialized compatibility requirements.
VMXNET3
VMXNET3 is VMware's preferred high-performance paravirtualized vNIC when the guest operating system and vSphere platform support it. VMware Tools supplies the required guest driver.
Compared with emulated adapters, VMXNET3 can reduce processing overhead and provide virtualization-aware optimizations such as:
- Jumbo-frame support.
- Hardware offloads, when supported throughout the network path.
- Multiqueue transmit and receive processing for improved parallelism on multi-vCPU systems.
- IPv6 offload capabilities.
- Other driver and platform optimizations intended for virtual networking.
VMXNET3 requires virtual hardware version 7 or later. VMware Tools must also be installed with a compatible VMXNET3 driver. Support for individual features can depend on the guest OS, driver version, ESXi or vSphere version, and configured VM features.
VMXNET3 is associated with support for capabilities such as fault tolerance and record/replay, but compatibility must be verified for the specific vSphere release and VM configuration.
VMware Virtual Network Adapter Comparison
| Adapter type | Adapter model or architecture | Guest driver source | Compatibility focus | Performance focus | Key capabilities | Important prerequisites | Typical use case |
|---|---|---|---|---|---|---|---|
| Flexible | Vlance; emulated AMD 79C970 PCnet32 LANCE, 10 Mbps | Legacy guest driver; VMware Tools can enable vmxnet behavior | Older 32-bit guests and broad legacy-driver compatibility | Limited compared with modern adapters | Compatibility identity; possible higher-performance vmxnet behavior with Tools | Suitable legacy driver; VMware Tools for vmxnet behavior | Legacy or specialized compatibility |
| E1000 | Emulated Intel 82545EM Gigabit Ethernet | Guest Intel-compatible driver | Broad operating system compatibility, including historical Windows XP and Linux kernel 2.4.19 or later examples | Reliable, but more emulation overhead | Familiar Intel hardware model | Guest must support the corresponding driver | Older guests or compatibility-first deployments |
| E1000E | Emulated Intel 82574L Gigabit Ethernet | Guest Intel e1000e-family driver | Guests such as Windows 8 and newer that support the model | Compatibility-oriented rather than maximum performance | Familiar Intel Gigabit hardware model | Guest support for the E1000E/e1000e device | Modern guest compatibility when VMXNET3 is unavailable |
| VMXNET2 | Enhanced virtualization-aware vmxnet adapter | VMware virtual networking driver | Supported older VMware guest environments | Higher performance than basic legacy behavior | Jumbo frames and hardware offloads | Compatible guest driver and platform | Older performance-focused or specialized deployments |
| VMXNET3 | High-performance VMware paravirtualized adapter | VMware Tools VMXNET3 driver | Supported modern guest operating systems | Lower overhead and high throughput | Jumbo frames, offloads, multiqueue, IPv6 offloads, and other optimizations | VMware Tools, compatible guest and platform, virtual hardware version 7 or later | Modern production workloads |
How to Choose an Adapter
Use this decision process before creating or modifying a VM:
- Check guest support. Determine whether the guest OS includes or can install a compatible VMXNET3 driver. If not, identify whether E1000, E1000E, or a legacy LANCE driver is available.
- Check VMware Tools. VMXNET3 requires the appropriate VMware Tools driver. Plan installation or updating before relying on the adapter.
- Check virtual hardware. Confirm that the VM's compatibility level supports VMXNET3, which requires virtual hardware version 7 or later.
- Identify workload requirements. Consider throughput, CPU efficiency, jumbo frames, hardware offloads, IPv6 processing, and multiqueue operation.
- Prefer VMXNET3 when compatible. It is the usual choice for modern supported Windows and Linux server VMs.
- Use emulated Intel hardware when necessary. Choose E1000 or E1000E according to the guest's available driver and compatibility requirements.
- Reserve Flexible and VMXNET2 for legacy cases. These adapters can be appropriate when an older guest or specialized configuration requires them.
| Condition | Recommended adapter | Why | Cautions |
|---|---|---|---|
| Modern supported guest with VMware Tools | VMXNET3 | Provides virtualization-aware performance and efficiency | Confirm driver, guest, platform, and virtual hardware support |
| Guest lacking VMXNET drivers | E1000 or E1000E | Emulated Intel hardware may be recognized without VMware-specific drivers | Select the model supported by the guest; accept additional emulation overhead |
| Legacy 32-bit guest | Flexible | Vlance offers broad old-driver compatibility | Not normally suitable as a modern performance choice |
| Need for maximum virtual networking performance | VMXNET3 | Paravirtualization can reduce overhead and improve packet processing | Performance also depends on vSwitch, uplinks, CPU, guest driver, and workload |
| Need for jumbo frames, offloads, or multiqueue | VMXNET3 where supported; VMXNET2 for an older supported requirement | These adapters provide virtualization-aware capabilities | Verify end-to-end MTU and feature support |
| VM does not meet the VMXNET3 hardware requirement | E1000 or E1000E until compatibility is upgraded | Emulated adapters avoid the VMXNET3 hardware prerequisite | Upgrade compatibility only after checking guest and platform impact |
Practical Selection Examples
Modern Windows or Linux server
Choose VMXNET3 when the guest supports VMware Tools and the VM meets the required virtual hardware level. Confirm that the guest recognizes the adapter, has a current driver, and can reach its network. If jumbo frames are configured, verify the MTU across the guest-to-network path.
Older guest without a VMXNET3 driver
Choose E1000 or E1000E according to the guest's available Intel-compatible driver. Confirm that the guest detects the device and that the selected driver is installed. If the operating system and VMware Tools are later upgraded, plan a controlled migration to VMXNET3.
Legacy 32-bit guest
Choose Flexible when the guest requires broad old-driver compatibility. Confirm that a PCnet32/LANCE driver is available. Install VMware Tools if the environment supports the higher-performance vmxnet behavior.
Migrating an existing adapter
A common migration is E1000 or E1000E to VMXNET3 after confirming guest support. Document the current settings, power off the VM when required, change the virtual hardware, and then verify the new interface and all network dependencies after startup.
Operational Considerations When Changing a vNIC
Before changing an adapter, document:
- Static IP address, subnet mask or prefix, default gateway, routes, and DNS settings.
- MAC-dependent licensing, access controls, firewall rules, DHCP reservations, and monitoring.
- Current port group, distributed port group, VLAN, connection state, and MTU.
- Interface name and any application or service bound specifically to that interface.
After the change, the operating system may create a new interface name or retain the old interface as an inactive device. Reapply or transfer IP settings as appropriate. Reinstall or update VMware Tools if the VMXNET3 driver is missing or outdated.
Post-Change Network Validation Checklist
| Check | What to verify | Common result if incorrect |
|---|---|---|
| Guest driver | The selected adapter has a compatible, functioning driver | Unknown Ethernet controller or no network device |
| Interface detection | The guest detects the new vNIC and assigns the expected interface | Old settings remain on another interface |
| IP configuration | Address, prefix or mask, and static or DHCP settings are correct | No local connectivity or duplicate addressing |
| Default gateway and routes | Expected routes and gateway are present | Local network works but remote networks do not |
| DNS resolution | DNS servers and resolver configuration are correct | Applications fail by name while IP tests work |
| VLAN and port group connectivity | The vNIC is connected to the correct port group, VLAN, and uplink path | No connectivity or access to the wrong network |
| MTU consistency | Guest, vNIC, virtual switch, physical network, and destination use a compatible MTU | Small packets work but jumbo-frame traffic fails |
| Application connectivity | Required services can communicate in both relevant directions | Network tests pass but production services remain unavailable |
Troubleshooting Adapter Problems
Unknown Ethernet controller after selecting VMXNET3
Likely causes include missing VMware Tools, an absent or outdated VMXNET3 driver, an unsupported guest OS, or a VM compatibility level below virtual hardware version 7.
- Verify guest OS and VM hardware compatibility.
- Install or update VMware Tools and its network driver.
- Use E1000 or E1000E temporarily if the guest cannot load a VMXNET3 driver.
Connectivity lost after replacing an adapter
The guest may regard the replacement as a separate interface, leaving the old static configuration attached to the previous device. Check interface enumeration, transfer or reapply network settings, and verify the port group, VLAN, connected state, default route, and DNS settings.
VMXNET3 does not deliver expected performance
Update VMware Tools and the guest driver first. Then inspect guest CPU utilization, vSwitch configuration, host networking, physical uplink capacity, and application behavior. Offloads or multiqueue may not be supported or active for the particular guest and platform versions.
Jumbo frames fail inconsistently
Jumbo frames require a consistent supported MTU from the guest through the vNIC, virtual switch, physical switches, uplinks, and destination interface. Verify every segment. If any device uses a smaller MTU, use a consistent supported MTU or return to the standard MTU.
Key Takeaways
- Flexible is primarily a legacy compatibility adapter that presents as Vlance.
- E1000 and E1000E emulate Intel Gigabit NIC models and are useful when guest driver compatibility is more important than efficiency.
- VMXNET2 is an older enhanced vmxnet option with jumbo-frame and offload capabilities.
- VMXNET3 is normally the best choice for a supported modern guest and requires VMware Tools plus virtual hardware version 7 or later.
- Changing a vNIC can create a new guest interface and can require IP, firewall, routing, DNS, monitoring, and application configuration changes.
- Validate the complete virtual and physical network path instead of judging performance from adapter type alone.
For a concise reference, see Types Of Virtual Network Adapters.