Subject: Re: [vserver] virt_load, virt_mem and vs 2.3.0.36
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Mon, 25 May 2009 13:18:37 +0200

On Mon, May 25, 2009 at 11:55:10AM +0200, Xavier Montagutelli wrote:
> Hello,

> Do virt_load and virt_mem work as expected in VServer 2.3.0.36 ? 
> Or do I misunderstand them ?

> Kernel used (compiled by ben@bristolwireless.net) : 
> 2.6.29.2-vs2.3.0.36.10-beng (OK, if I have time, I will compile 
> my own kernel ...)

> 1) virt_load : "monvs" and "nono" are two VServers with virt_load
> activated 

> # cat /etc/vservers/monvs/flags
> virt_mem
> virt_load

> I run "burnMMX" inside both VServers : the load average is the 
> same under the VServers and the host, around 1.9, each burnMM 
> process consuming aroud 50 % of my CPU.

expected for this kernel, get vs2.3.0.36.13 and the
load virtualization should work as expected

> Same thing when I activate "sched_hard" : in this case, I would 
> expect the load average to stay at 1 inside the VServers, and each 
> burnMMX appearing as consuming 100% of the (allocated slice of the) CPU

> 2) virt_mem : with VServer version 2.0, the "swap" size displayed 
> inside a VServer used to be "AS.hard - RSS.hard".

correct, we changed that :)

> Now, the memory is displayed virtualized (as expected equal to 
> RSS.hard), but the swap is always 0.

it is now the difference between RSS.hard and RSS.soft

HTC,
Herbert

> -- 
> Xavier Montagutelli                      Tel : +33 (0)5 55 45 77 20
> Service Commun Informatique              Fax : +33 (0)5 55 45 75 95
> Universite de Limoges
> 123, avenue Albert Thomas
> 87060 Limoges cedex