VC 2.0.1 and ESX 2.5

[neil_murphy]

Hi,

I have started a two week process of upgrading from VC1.3/ESX2.5.4 to VC2.0.1/ESX23.0.1.

I started by upgrading to VC2.0.1 build 32042. I added my ESX2.5.4 servers and everything was fine, VMotion working and performance fine. Then I noticed there was a VC upgrade available to bring this up to build 40644. After the upgrade I logged into VC. The first shock I got was that the ESX2.5.4 hosts were dsconnected pending a VirtualCenter Agent upgrade. When they came back on line I got my second shock - memory utilisation had gone through the roof giving me warnings on both ESX hosts. Closer inspection reveals that the Memory Granted figure for every VM has gone up to nearly the assigned memory and never comes down.

Has anyone any ideas why this may be happening?

Neil.

[dsouza_r · Accepted solution]

That's odd because according to VMware:

"This update resolves several issues associated with VirtualCenter’s database server; issues related to VirtualCenter 1.x compatibility mode; and memory consumption and reporting issues"

Did you read this

http://www.vmware.com/support/vi3/doc/vc-201-200702-patch.html#limitations

Cheers,

Roland

[neil_murphy]

Hi Roland,

That's exactly what happened. It turns out that the hosts were always under pressure according to the MUI but this wasn't reflected in VC until the latest patch was applied.

Regards,

Neil.