Windows Server 2019 GuestOS is experiencing vNIC reboots with a windows event 10400
GuestOS (Win Server 2019) will begin throwing a warning event of 10400 stating that “The network interface has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver detected that its hardware has stopped responding to commands. This network interface has been reset X times since it was last initialized.”
GuestOS will also list warning event of 27 e1iexpress stating that the network link is disconnected.
After throwing that first error, the vNIC will begin to reboot nearly every 60 seconds until the vNIC is either disabled and then re-enabled via the device manager, or until the server itself has been rebooted. It [vNIC] can reboot as many as 6000 times in a single night, all with only a warning level event, causing the server to be completely network isolated.
The issue has taken as much as a week to re-present itself, and as little as less than 24 hours after a fresh reboot.
Attempting to test the use of Networking via VMXNET 3 instead of e1000e.
Since e1000e was previously being supported by generic Windows drivers, and was emulating an older Intel card that doesn’t have good Server 2019 drivers, I’m attempting to use VMXNET 3 instead.
The drivers listed for VMXNET 3 are made by VMware and state that they’re approved by Microsoft. Here’s to hoping this is the solution needed.
Quoted text from the compatibility guide via VMware:
Networking
| e1000: | Not Supported | Emulated Intel 82545EM Gigabit Ethernet NIC |
| e1000e: | Supported | Emulated Intel 82574L Gigabit Ethernet Controller |
| Enhanced VMXNET: | Not Supported | Second generation VMware virtual NIC |
| Vlance: | Not Supported | Emulated AMD 79C970 PCnet32 Lance NIC |
| VMXNET: | Not Supported | VMware virtual NIC |
| VMXNET 3: | Supported (Recommended) | Third generation VMware virtual NIC |