[VMware cloud on AWS] SDDC Version 1.8 or 1.8 v2. Virtual Machines configured with a vmxnet3 NIC might hang or consume excessive CPU cycles.
Article ID: 329719
Updated On:
Products
VMware Cloud on AWS
Issue/Introduction
Symptoms:
SDDC Version 1.8 or 1.8 v2. Virtual Machines configured with a vmxnet3 NIC might hang or consume excessive CPU cycles.
SDDC Version 1.8 or 1.8 v2. Virtual Machines configured with a vmxnet3 NIC might hang or consume excessive CPU cycles.
Cause
Virtual Machines configured with the vmxnet3 network interface controller (NIC) might hang.
The issue is due to a bug in the handling of legacy interrupts.
The bug mainly impacts older Windows operating systems e.g. Windows 2003, however other guest operating systems configured with vmxnet3 may be susceptible to hanging under certain conditions, either during shutdown, startup, PXE booting the OS over the network or if a large number of NICs are configured. Linux operating systems have not been observed to hang but have been observed to consume excessive CPU cycles
The issue is due to a bug in the handling of legacy interrupts.
The bug mainly impacts older Windows operating systems e.g. Windows 2003, however other guest operating systems configured with vmxnet3 may be susceptible to hanging under certain conditions, either during shutdown, startup, PXE booting the OS over the network or if a large number of NICs are configured. Linux operating systems have not been observed to hang but have been observed to consume excessive CPU cycles
Resolution
This is a known issue.
Workaround:
Do not use vmxnet3 and instead configure the guest to use the e1000 NIC instead
Workaround:
Do not use vmxnet3 and instead configure the guest to use the e1000 NIC instead
Feedback
Yes
No
Powered by
