Subject: Re: [vserver] vserver guest memory usage: cache/buffers?
From: Steve Kieu <msh.computing@gmail.com>
Date: Wed, 30 Nov 2011 09:10:59 +1100
Wed, 30 Nov 2011 09:10:59 +1100
I assume that you have read the doc - and install a clean vserver env - and
recent enough vserver tools. The version I mentioned in previous email auto
mount the cgroup for you so check:

ls /dev/cgroup/VS_NAME/

you should see many memory.XXX files with settings inside.

If not then something wrong, cgroup not mounted - util vserver not started
etc../ Refer to the doc again then.

Also check if you set it up

ls /etc/vservers/VS_NAME/dlimits/root/
directory  inodes_total  reserved  space_total

I would suggest you can build a new machine - using valinal kernel
2.6.32.48 in my case it works - grep the vserver patch, build it and grep
recent vserver tools, - I have the x86_64 rpm here if you want - then
started from scratch.

best luck


On Wed, Nov 30, 2011 at 6:57 AM, Jarry <mr.jarry@gmail.com> wrote:

> On 29-Nov-11 0:58, Steve Kieu wrote:
>
>> what is the error - steps that you could not use cgroup?
>>
>
> The only error is that it simply does not work. When I use
> cgroups for memory-limits, free/top and similar tools in
> vserver-guest always show full real hardware memory.
> As if there were no limits in memory.limit_in_bytes
> and memory.memsw.limit_in_bytes. VIRT_MEM is activated.
>
> And what is even worse, it seems there are actually
> no limits at all. vserver-stat show that vs-guest
> takes more memory than I allowed. But the "old way"
> (rss.soft, rss.hard) at least works. Strange...
>
>
> Jarry
> --
> ______________________________**______________________________**___
> This mailbox accepts e-mails only from selected mailing-lists!
> Everything else is considered to be spam and therefore deleted.
>



-- 
Steve Kieu


I assume that you have read the doc - and install a clean vserver env - and recent enough vserver tools. The version I mentioned in previous email auto mount the cgroup for you so check:

ls /dev/cgroup/VS NAME/

you should see many memory.XXX files with settings inside.

If not then something wrong, cgroup not mounted - util vserver not started etc../ Refer to the doc again then.

Also check if you set it up

ls /etc/vservers/VS NAME/dlimits/root/
directory  inodes total  reserved  space total

I would suggest you can build a new machine - using valinal kernel  2.6.32.48 in my case it works - grep the vserver patch, build it and grep recent vserver tools, - I have the x86 64 rpm here if you want - then started from scratch.

best luck


On Wed, Nov 30, 2011 at 6:57 AM, Jarry <mr.jarry@gmail.com> wrote:
On 29-Nov-11 0:58, Steve Kieu wrote:
what is the error - steps that you could not use cgroup?

The only error is that it simply does not work. When I use
cgroups for memory-limits, free/top and similar tools in
vserver-guest always show full real hardware memory.
As if there were no limits in memory.limit in bytes
and memory.memsw.limit in bytes. VIRT MEM is activated.

And what is even worse, it seems there are actually
no limits at all. vserver-stat show that vs-guest
takes more memory than I allowed. But the "old way"
(rss.soft, rss.hard) at least works. Strange...


Jarry
--

This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.



--
Steve Kieu