[Lxc-users] one or two things

[atp]

Hi,

A fuse file system has other drawbacks. /proc/self points to the fuse
pid, not to the pid of the calling process. Fuse wants to know the 
file size before it will hand back the data. Check out the file sizes
reported by ls -l /proc and you'll see a mishmash. Most report 0 length
in stat.st_size. 

The current thought is a new file system in kernel space, that
essentially does what the fuse code does. For an example, see the
unionfs. 

Ideally, we'd go the route of openvz and change the procfs itself to be
virtualisation aware. Its partially there, in that the PID namespace
works, but the control group masking - memory, cpus etc does not. I
understand from talking to others that there are some objections to that
from the great and the good, so a new filesystem seems a better step for
now. 

The procfs_stat patch is a quick fix I've got for my own project, the
procfs-1.? are experiments building on the procfs-1.0 on the lxc site. 
There are a couple of bug fixes and enhancements, but they're
experimental. 

Andy


On Wed, 2010-06-16 at 13:44 +0200, lxc at zitta.fr wrote:
> Hi,
> 
> Talking about procfs's patches...
> Why not create a copy (let's call it lxcproc) of fs/proc in kernel code?
> 
> This copy could have all neccessary patches applied (memory and cpu views).
> So we could "mount -t lxcproc none /proc" in containers.
> 
> I think, it's a cleaner way than fuse overlay.
> 
> Regards,
> 
> Guillaume
> 
> Le 15/06/2010 11:52, atp a écrit :
> > Hi,
> >
> >  If anyone is interested, I've put the script(s) I use to create fedora
> > core 12 containers up on;
> >
> > http://www.tinola.com/lxc/
> >
> >  It needs the latest git version of lxc. 
> >
> >  I've also included a temporary patch to fs/proc/stat.c (tested on
> > 2.6.34) that masks the set of visible cpus to only those in the
> > containers cpuset.cpus. 
> >
> >  Andy
> >
> > 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.
> >
> > ------------------------------------------------------------------------------
> > ThinkGeek and WIRED's GeekDad team up for the Ultimate 
> > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
> > lucky parental unit.  See the prize list and enter to win: 
> > http://p.sf.net/sfu/thinkgeek-promo
> > _______________________________________________
> > Lxc-users mailing list
> > Lxc-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/lxc-users
> >   
> 
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate 
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
> lucky parental unit.  See the prize list and enter to win: 
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> 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.