Memory leak in the netGPHeap in ESXi 6.5. x and 6.7.x

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• The netGPHeap is used up and whole networking does not function.
• A Purple Diagnostic Screen is experienced.
• vMotion might be failed due to "out-of-memory" of netGPHeap.
• In the /var/log/vmkwarning.log file and /var/log/vmkernel.log file of the affected ESXi host, you see entries similar to:
  
  2019-02-09T12:54:39.275Z cpu1:1854625)WARNING: VMotionSend: 3500: 4994880729895066355 D: failed to get DVS state in the restore phase from the source host <3.0.0.17>
  2019-02-09T12:54:39.275Z cpu1:1854625)WARNING: VMotionSend: 5809: 4994880729895066355 D: Failed handling message reply 0: Out of memory
  2019-02-09T12:54:39.275Z cpu1:1854625)WARNING: Migrate: 273: 4994880729895066355 D: Failed: Out of memory (0xbad0014) @0x418025e880c2
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vSphere ESXi 6.5
VMware vSphere ESXi 6.7

Cause

This issue occurs due to memory leaks of container port vMotion.

Resolution

This issue is resolved in VMware vSphere ESXi 6.5 Update 3 and ESXi 6.7 Update 2, available at VMware Downloads