Re: Memory problems

[lsorense@csclub.uwaterloo.ca (Lennart Sorensen)]

On Thu, Jun 03, 2010 at 04:56:21PM +0200, Jonatan Soto wrote:
> Here it is (eg: Server1):
> 
> target:               503386 pages
> current:              503386 pages

So that looks like the vmware balloon driver has aquired 503386 pages
(at 4KB each) which would be your 2GB missing memory.

So because your host is low on ram it has asked your guest to give
back 2GB.  So if you want your guests to not have their ram borrowed
back to the host, add more ram to the host, or make sure the guests run
identical code so that vmware can merge more identical pages (not very
likely to be possible).

> rateNoSleepAlloc:      16384 pages/sec
> rateSleepAlloc:         2048 pages/sec
> rateFree:              16384 pages/sec
> 
> timer:               1135686
> start:                     1 (   0 failed)
> guestType:                 1 (   0 failed)
> lock:                2518801 (  54 failed)
> unlock:              2015361 (   0 failed)
> target:              1135686 (   0 failed)
> primNoSleepAlloc:    2518801 (   0 failed)
> primCanSleepAlloc:         0 (   0 failed)
> primFree:            2015361
> errAlloc:                 51
> errFree:                  51
> 
> Is primFree the total amount of free memory available?

No idea what units those are in.

So the vmware balloon driver is in fact the thing that made your ram
disppear.  Since it is a kernel driver you of course won't see a process
using the ram, it will simply be marked in use.

-- 
Len Sorensen