Today a customer called about a problem with the Exchange VM. For some reason the ESX Host where this VM resided was always swapping/ballooning. They checked and double checked the settings but could not find the problem. After a quick scan I noticed that there were limits set on memory for each VM. This particular VM had 1536MB of memory and a limit of 1024MB. After changing the setting back to it’s default setting, “unlimited”, the message was gone. I haven’t got a clue why this setup this way, limitting the memory to the exact amount assigned to a VM… weird, but problem solved.
Hi
I’ve had the same. Sometimes when you clone a VM and then change the memory or cpu settings, it just keeps the number of shares or limits. Looks like a bug in VC 2.0.x
Gabrie
I noticed this problem on all systems that were created pre 2.x, who later had their memory increased. It seems when 2.x or 2.5 was installed, it created Custom shares and manual memory limits based upon the memory at the time. When the memory was increased, VC stuck with the original memory utilization.
Hello,
We noticed the same issue while preparing VMs from a template that had limits on memory.
This issue was visible only on 64Bits VMs.
It was also getting his CPU time to the top while just doing a simple copy of files in explorer.
As soon as you release that limit, everything gets back to normal.