Memory Granted at 100%

[ToddWeber]

All of my ESX 3.x server's memory granted is sitting at 100%. Using vCharter Pro, I am always being warned that memory granted vs.server consumed is too high. Actual memory utilization is low (16.6%) on an ESX server with 23GB physical RAM and 8 running VM's (avg. active 952MB, no balloon, no swapping). So my question is, is memory granted at 100% usual/typical behaviour?

[mike_laspina]

Hello,

It's hard to tell what's happening from just the chart.

Can you post the file created by this command on the console.

esxcfg-info -r > esxresinfo.txt

It will describe every mem/disk/cpu resource allocation.

[ToddWeber]

Mike: here is the output, what do you think?

[mike_laspina]

I see some settings which are less than optimum.

You have resource limits on your VM's yet there is excess ram which could be allowed to participate.

Set your VM's as shown. This will let the host manage the resource more optimally.

[ToddWeber]

According to Virtual Center, the VM's are already set to unlimited. Do you think the ESX servers themselves have settings that do not match what Virtual Center is reporting?

[mike_laspina]

There is an issue but I'm not sure why your VC displays unlimited.

Here is what you esxcfg-info output shows for

|----Config File................................../vmfs/volumes/46e086ef-4c9a0d8f-f369-0016356bc5bf/EAIAS/EAIAS.vmx

\==+Memory Allocation :

|----Valid..................................true

|----Minimum................................0

|----Min Limit..............................110592

|----Maximum................................262144

|----Shares.................................normal

|----Units..................................kb

On my hosts I have the following showing.

\==+Memory Allocation :

|----Valid..................................true

|----Minimum................................0

|----Min Limit..............................unlimited

|----Maximum................................unlimited

|----Shares.................................normal

|----Units..................................kb

Connect directy to the esx server using the VI client and see what it reports there.

[ToddWeber]

VMWare tech support is looking into why ESX and VI Center report different values, there may be a known bug in there. In any case, I think the settings are correct, although MIN LIMIT is still set on the individual VM's, I don't know how (if possible) to modify that value to match yours (unlimited).

\==+Memory Allocation :

|----Valid..................................true

|----Minimum................................0

|----Min Limit..............................108544

|----Maximum................................unlimited

|----Shares.................................normal

|----Units..................................kb

[mike_laspina]

I have seen mismatched state info in other areas between ESX and the VC from time to time. Most of the time a host disconnect and reconnect clears the issue because the VC will need to query the ESX vmdb for it's current state once it connects and it updates the VC db with the newly acquired state info. Disconnecting and reconnection will not harm the vms.