Re: [RFC][PATCH 1/5] Virtualization/containers: startup

[Kirill Korotaev]

> > > How do we want to create the container?
> > > In our patch we did it through a /proc/container filesystem.
> > > Which created the container object and then on fork/exec switched over.
> >
> > this doesn't look good for a full virtualization solution, since proc
> > should be virtualized as well :)
>
>
> Well, /proc should be "virtualized" or "isolated", how do you expect a
> container to work correctly ? plenty of user space tools depend on it.
Sorry, not actually understand your question... :(
There is not much problems with virtualization of proc. It can be 
virtualized correctly, so that tools are still working. For example, in 
OpenVZ /proc has 2 trees - global and local.
global tree contains the entries which are visiable in all containers.
and local tree - only those which are visible to containers.
PIDs are shown also only those which present in container.

Kirill

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/