| Re: How is the privvmpages limit reached? [message #27116 is a reply to message #27101] |
Sun, 10 February 2008 01:58   |
Wheel
Messages: 3
Registered: February 2008
|
Junior Member |
|
|
Hi,
Thank you for your reply.
I read your post, but I do yet not fully understand why the Xen vps doesn't have memory problems.
(Correct me if I'm wrong.)
On the XEN vps it is able to allocate at most 768mb (guaranteed+swap). And on the OpenVZ vps it is able to allocate at least 403mb (98304 vmguarpages barrier) and at most 805mb (196608 privvmpages barrier).
To me it looks like the OpenVZ did not yet reach the privvmpages barrier, (since has a higher privvmpages barrier than the unfailed Xen VPS), but it did fail.
The doc says:
| Quote: |
If the current amount of allocated memory space exceeds the guarantee but below the barrier of privvmpages, allocations may or may not succeed, depending on the total amount of available memory in the system.
|
So can I conclude that the OpenVZ space has too little available memory in the hardware node? Or might there also be another reason?
[Updated on: Sun, 10 February 2008 01:58] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
