I wrote about two weeks ago and back in March but the issues with false memory alerts due to large pages being used have finally been solved.
Fixes an issue where a guest operating system shows high memory usage on Nehalem based systems, which might trigger memory alarms in vCenter. These alarms are false positives and are triggered only when large pages are used. This fix selectively inhibits the promotion of large page regions with sampled small page files. This provides a specific estimate instead of assuming a large page is active when one small page within it is active.
BEFORE INSTALLING THIS PATCH: If you have set Mem.AllocGuestLargePage to 0 to workaround the high memory usage issue detailed in the Summaries and Symptoms section, undo the workaround by setting Mem.AllocGuestLargePage to 1.
Six patches have been released today but this fix was probably the one that people talk about the most that’s why I wanted to make everyone aware of it! Download the patches here.
rickymh says
Thanks Duncan!
Patch time!
jimau says
Is there a similar fix for 3.5 or is it only available on ESX4.0?
DonB says
I was wondering if a patch was available for 3.5 as well…
Using Update Manager I am up to date as of this past Sunday on my AMD/Nehalem ESX 3.5 nodes bt all my Win2K8 x64 servers are still in alarm 🙁