Messages in this thread | | | Date | Sun, 05 Feb 2006 10:39:51 -0500 | From | Hubertus Franke <> | Subject | Re: [RFC][PATCH 1/5] Virtualization/containers: startup |
| |
Kirill Korotaev wrote: >> 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 :)
Just lazy's man's development version of a faked sys_call to create the container without having to go through all architectures ... Nothing permanent..
> >> How about an additional sys_exec_container( exec_args + >> "container_name"). >> This does all the work like exec, but creates new container >> with name "..." and attaches task to new container. >> If name exists, an error -EEXIST will be raised ! > > Why do you need exec?
(a) how do you create/destroy a container (b) how do you attach yourself to it?
-- Hubertus
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |