Maciek Kaliszewski wrote:
Gordan Bobic wrote:
On 16/08/2009 13:42, Pablo Sanchez wrote:
[ Comments below, in line ]
On Sunday 16 August 2009 at 7:17 am, Gordan Bobic penned
about "[vbox-users] Memory Overcommit and Recursive Paging"
I've noticed problems when running more than one guest (one XP64 and
one
XP32 in this instance, haven't tried other configurations). I have a
4GB
machine and I set each guest up with 2GB of RAM. Recursive paging was
also enabled in each. What ends up happening is that somehow all 4GB of
RAM end up being used up and swap usage rapidly grows to 4GB as well
(so
8GB in total!). Needless to say, everything completely grinds to a
halt.
Is this a known bug/problem/limitation?
It's by design. The VM will allocate all the RAM at startup. Search
the archives as this subject was brought up one other time, about a
couple of months ago.
That still doesn't explain how come with 2x 2GB VMs the machine ended
up immediately using up 4GB of RAM + 4GB of swap. It is as if all of
the VM memory was getting allocated twice in this instance. Disabling
recursive paging seemed to solve the problem.
Hi ,
I'm follow this list ,but I'm not a Vbox hacker so I may be wrong :-) .
AFAIN Vbox allocates physical ram and mark it unswapable ,so behavior
you described seems justified :-).
Not quite - it doesn't explain how come 4GB of swap ended up being used
since there were no apps using that much RAM, maybt 200MB at most. And
the VMs ground to a halt more than the rest of the machine, so it looks
like the VM memory did in fact get swapped out.
Gordan
_______________________________________________
vbox-users mailing list
vbox-users@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-users
