Solved

VMWARE balloon issue

Posted on 2011-09-27
3
823 Views
Last Modified: 2012-05-12
I am getting high cpu utlization on some of my guests they are windows 2003 boxes . attached is the ballooned ram info and the memory configuration of the guest , I know that this is due to some misconfig on the memory , but not sure what to do next  sss
0
Comment
Question by:NAMEWITHELD12
3 Comments
 
LVL 1

Author Comment

by:NAMEWITHELD12
ID: 36713292
I think i know what is going on the guest is allocated 2gb ram , but it is limited at the resource pool at 1gb so ......
0
 
LVL 23

Assisted Solution

by:bhanukir7
bhanukir7 earned 100 total points
ID: 36716501
hi

VMware balooning is applied only when there is limited memory on the ESX server (memory over commit) and not based on the limits.

so you may want to check if this machine is part of any cluster or resource pool where there is memory limit

or if the over all memory usage on the physical ESX host is higher than 80%

regards
bhanu
0
 
LVL 23

Accepted Solution

by:
Mysidia earned 400 total points
ID: 36896329
This panel shows  "Limit:  1.00gb"   "Configured: 2.00gb"

In other words, the VM is configured for 2gb of RAM,  but a  Limit of  1gb has been applied to the VM.

The OS running in the VM has no idea about that "1gb limit",  therefore, the guest OS will attempt to use the entire 2gb,  resulting  in ballooning,  or swapping   of the portion of private memory used minus the VM's limit  by the hypervisor in order to enforce the limit.

Because this configuration doesn't actually relieve memory pressure in the guest OS, and creates a performance penalty, due to the hypervisor having to apply ballooning or swapping, it is strongly recommended that you change the VM's configured memory to 1gb,  OR remove the limit from the VM under  Edit Settings >  Resources > Memory.


There are situations where memory limits are suitable,  but in general they are not, and aggregate performance is much better when configuring  resource pools, memory share values,  and reservations,  for the VMs that need memory with higher priority rather than attempting to set a limit on lower priority VMs.

Share priorities apply when there is resource contention on the host.

Resource limits ALWAYS apply;  even if there is 30gb of RAM free on the host,
a VM with  2gb of memory assigned and limited to 1gb  can balloon and swap.



0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.
When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
Teach the user how to use create log bundles for vCenter Server or ESXi hosts Open vSphere Web Client: Generate vCenter Server and ESXi host log bundle:  Open vCenter Server Appliance Web Management interface and generate log bundle: Open vCenter Se…
Advanced tutorial on how to run the esxtop command to capture a batch file in csv format in order to export the file and use it for performance analysis. He demonstrates how to download the file using a vSphere web client (or vSphere client) and exp…

919 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now