[Lxc-users] not separeted resources

[atp]

Hi,

> I'm wondering on some problems, come up in the near past using LXC. All 
> of our systems are Ubuntu 10.04 (2.6.32-server) with lxc 0.7.1.
> 
> 1. Why does the container see the host's dmesg? Why does it don't have 
> own one?

  Because the work to create per namespace kernel ring buffers has not
been done. Its not clear whether a new namespace is the best approach.

> 
> 2. Why does the container see the host's /proc/partitions? Munin's 
> diskstats plugin show all the partitions of the host.

   /proc has not been made fully container aware. An attempt to do this
using a FUSE file system was made, but was discontinued once the
technical problems with this approach became obvious. 

   At the moment process ID files in /proc/ are namespace aware. The
remaining files are not. 

> 
> 3. Why does host's apparmor (and probably selinux) have influence to the 
> containers process-es?
> 

   Its the same kernel image that runs both the host and the
containers. 

> 4. Why does container see the host's memory and swap usage? Is there any 
> tool to check only the container related informations? Is there any tool 
> like 'xm top' (top like tool to show VM's related statistics)?
> 
   
   Same answer as 2).

   Per container/per cgroup resource tracking has not been implemented. 

> 
> Probably there will be more, right now this is in my mind:)

   HTH.

        Andy

> 
> Thank you,
> 
> tamas
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Lxc-users mailing list
> Lxc-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
Andrew Phillips
Head of Systems

www.lmax.com 

Office: +44 203 1922509
Mobile: +44 (0)7595 242 900

LMAX | Level 2, Yellow Building | 1 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.