Hi everyone,
I'm experiencing a strange behaviour on ESX 3.0.3, 104629 server.
It is just installed, only 3 VM running on it,
48GB of physical RAM in the ESX,
and ...
some VMs are already using the balloon driver and the ESX even swaps.(see below)
I thought only low memory condition on the ESX would trigger the ballooning (around 75%), or memory overcommitment.
Can someone shed some light on this ?
here is an extract of an esxtop :
4:37:00pm up 9 days, 5:24, 65 worlds; MEM overcommit average: 0.00, 0.00, 0.00
PMEM (MB): 49149 total: 800 cos, 427 vmk, 4925 other, 42996 free
VMKMEM (MB): 47528 managed: 2851 minfree, 4058 rsvd, 43325 ursvd, high state
COSMEM (MB): 234 free: 4000 swap_t, 4000 swap_f: 0.00 r/s, 0.00 w/s
PSHARE (MB): 3884 shared, 281 common: 3603 saving
SWAP (MB): 109 curr, 96 target: 0.00 r/s, 0.00 w/s
MEMCTL (MB): 155 curr, 155 target, 5543 max
ID GID NAME NMEM MEMSZ SZTGT TCHD %ACTV %ACTVS %ACTVF %ACTVN MCTL? MCTLSZ MCTLTGT MCTLMAX SWCUR SWTGT SWR/s SWW/s
12 12 vmware-vmkauthd 1 2.20 2.20 0.34 0 0 0 0 N 0.00 0.00 0.00 0.00 0.00 0.00 0.00
18 18 VM1 7 3920.00 3328.65 270.82 3 2 2 0 Y 51.04 51.04 2548.00 8.28 1.31 0.00 0.00
21 21 VM2 7 1024.00 706.27 78.87 10 4 8 8 Y 38.15 38.15 665.60 3.31 0.66 0.00 0.00
22 22 VM3 13 3584.00 886.62 105.54 0 0 0 0 Y 66.00 66.00 2329.60 98.09 22.22 0.00 0.00
Olivier