[Lxc-users] How make top, meminfo etc. to show the limits of the container?

2011-01-21 Thread GMail Christian
Hi,

Is there already a way of hiding the hosts full RAM and SWAP info from 
the containers and make top, meminfo, etc. in the containers show the 
correct limits?

thx,
christian

--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] How make top, meminfo etc. to show the limits of the container?

2011-01-21 Thread atp
Hi,

Its not as simple as it seems. What you're asking for is to selectively
hide or modify what gets shown to container processes by the /proc file
system. In other words making /proc container aware. /proc is already
partially there - with the pid namespace, but not for ram and cpus. 

We've tried a couple of approaches - FUSE based overlay file system etc
- and at the last lxc dev call the way forward was proposed as being an
in kernel file system integrated with the cgroups subsystem, bind
mounted to the containers /proc.

At the moment, the containers I'm running adopt a far more hacky
solution to this by patching the /proc filesystem itself. 

Patch for cpu limiting proc stat is at;
http://www.tinola.com/lxc/

HTH
Andy

On Fri, 2011-01-21 at 09:24 +0100, GMail Christian wrote:
 Hi,
 
 Is there already a way of hiding the hosts full RAM and SWAP info from 
 the containers and make top, meminfo, etc. in the containers show the 
 correct limits?
 
 thx,
 christian
 
 --
 Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
 Finally, a world-class log management solution at an even better price-free!
 Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
 February 28th, so secure your free ArcSight Logger TODAY! 
 http://p.sf.net/sfu/arcsight-sfd2d
 ___
 Lxc-users mailing list
 Lxc-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/lxc-users

-- 
Andrew Phillips
Head of Systems

Direct: +44 (0)203 192 2509
Mobile: +44 (0)7595 242 900

LMAX, Yellow Building, 1A Nicholas Road,  London, W11 4AN



The information in this e-mail and any attachment is confidential and is 
intended only for the named recipient(s). The e-mail may not be disclosed or 
used by any person other than the addressee, nor may it be copied in any way. 
If you are not a named recipient please notify the sender immediately and 
delete any copies of this message. Any unauthorized copying, disclosure or 
distribution of the material in this e-mail is strictly forbidden. Any view or 
opinions presented are solely those of the author and do not necessarily 
represent those of the company.

--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users


Re: [Lxc-users] How make top, meminfo etc. to show the limits of the container?

2011-01-21 Thread Serge Hallyn
Quoting atp (andrew.phill...@lmax.com):
 Hi,
 
 Its not as simple as it seems. What you're asking for is to selectively
 hide or modify what gets shown to container processes by the /proc file
 system. In other words making /proc container aware. /proc is already
 partially there - with the pid namespace, but not for ram and cpus. 
 
 We've tried a couple of approaches - FUSE based overlay file system etc
 - and at the last lxc dev call the way forward was proposed as being an
 in kernel file system integrated with the cgroups subsystem, bind
 mounted to the containers /proc.
 
 At the moment, the containers I'm running adopt a far more hacky
 solution to this by patching the /proc filesystem itself. 
 
 Patch for cpu limiting proc stat is at;
 http://www.tinola.com/lxc/

Sentiments in kernel community tend to change profoundly over any
3 year period.  I think it's worth floating patches like your proc
patch on lkml for review.

-serge

--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users