VMware understands the critical impact of this issue on its customers. The root cause has been identified.
This is a known issue affecting VMware vSphere (ESXi 5.5 Update 3, ESXi minor releases after Update 3b, ESXi 6.0, ESXi 6.0u1, or ESXi 6.0u1a).
This issue is resolved in:
- ESXi 5.5 Update 3b, available at VMware Downloads. For more information, see the VMware ESXi 5.5 Update 3b Release Notes, and the Patch Release notice, VMware ESXi 5.5, Patch Release ESXi550-201512001 (2135410).
Important: Due to a change merge process error, subsequent ESXi 5.5 minor releases do not contain this fix. This is fixed in VMware ESXi 5.5, Patch Release ESXi550-201612001 (2147788) - Build 4722766.
For more information about downloading patches, see How to download patches in Customer Connect (1021623).
The affected releases are:
- ESXi 6.0 Update 1b and later, available at VMware Downloads. For more information, see the VMware ESXi 6.0 Update 1b Release Notes.
If you are unable to upgrade and you are running one of the affected versions of VMware vSphere ESXi listed above and the SAP Host Agent (SAP Host Agent 7.21 PL5 or later), VMware strongly recommends you open a support request to engage direct assistance by a VMware Technical Support Engineer to review the issue and implement the most appropriate resolution option. Mention this document to the responding Technical Support Engineer. For details on opening a support request, see
How to file a Support Request in Customer Connect (2006985).
To avoid experiencing this issue when using a third-party monitoring and statistics solution, postpone upgrading to vSphere 5.5 Update 3 or vSphere 6.0.x until an upgrade for your version of ESXi is available which fixes the issue. If you are already running ESXi 5.5 U3 or vSphere 6.0.x, your environment may not be affected if your statistics solution does not use VMware Extended Guest Statistics. Review the Administration guide and release notes of your third party statistics solution to see if the release you plan to install utilizes VMware Extended Guest Statistics. If yes, postpone the installation or upgrade of the solution or implement the workaround option until an upgrade for your version of ESXi is available which fixes the issue.
To work around this issue, you may perform a vMotion migration of the virtual machine between ESXi hosts to temporarily clear the memory leak. VMware recommends that this migration should happen at least once each week. If your environment doesn't already migrate the affected virtual machines often enough, you can automate the migrations using a Schedule Task operation.
A scheduled task can be used to periodically and automatically relocate the affected virtual machines. As stated, VMware recommends scheduling these tasks on a weekly basis. However, depending on the activity and load of the virtual machine(s), the scheduled task may need to be more frequent. For more information on creating a scheduled task for vMotion migration, see the
Schedule Tasks section of the
vSphere 6.0 vCenter Server and Host Management Guide.
This article will be updated as soon as the regular patch release is available. You may subscribe to this article for RSS updates using the
Subscribe to Document link in the Actions box.