Virtual Machine Network Connection Fails on ESXi Prior to 7.0 U2c

Products

• VMware vSphere ESXi

Issue/Introduction

• Virtual Machine network connection fails on ESXi prior to 7.0 U2c.
• The following message is recorded in the vmkernel log when the connection between the virtual machine's NIC and the vDS is disconnected.

XXXX-XX-XXTXX:XX:XX.XXXZ cpuXX:1062121)WARNING: PsMsg: 202: out of memory, can't post msgID 0x0:0x100
XXXX-XX-XXTXX:XX:XX.XXXZ cpuXX:1062121)Net: 3575: dissociate dvPort XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX from port 0x4000016
XXXX-XX-XXTXX:XX:XX.XXXZ cpuXX:1062121)Net: 3581: disconnected client from port 0x4000016

• Restarting the virtual machine does not resolve the issue, and the following message continues to be recorded in the vmkernel log.

XXXX-XX-XXTXX:XX:XX.XXXZ cpuXX:237122879)NetPortset: 2924: Failed to alloc port by portID 0x4000017
XXXX-XX-XXTXX:XX:XX.XXXZ cpuXX:237122879)Net: 2155: can't connect XXXXX.eth0  to vDS: Out of memory

Environment

ESXi 7.0 U2

Cause

This issue occurs due to memory leaks for pktlist in portset world data.  

Resolution

This issue has been resolved in VMware ESXi 7.0 Update 2c.

Workaround:
In case an update to ESXi 7.0 U2c or newer is currently not possible, you can use one of the following options:

1. Power off the VM and perform cold migration.
2. Reboot the host.

Additional Information

vMotion fails with Status - Failed waiting for data. Error 195887124. Out of memory Heap portsetHeap already at its maximum size.