Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751769AbWBEPj6 (ORCPT ); Sun, 5 Feb 2006 10:39:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751770AbWBEPj6 (ORCPT ); Sun, 5 Feb 2006 10:39:58 -0500 Received: from e2.ny.us.ibm.com ([32.97.182.142]:45282 "EHLO e2.ny.us.ibm.com") by vger.kernel.org with ESMTP id S1751769AbWBEPj5 (ORCPT ); Sun, 5 Feb 2006 10:39:57 -0500 Message-ID: <43E61C47.8070905@watson.ibm.com> Date: Sun, 05 Feb 2006 10:39:51 -0500 From: Hubertus Franke User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kirill Korotaev CC: Greg KH , Dave Hansen , Linus Torvalds , Kirill Korotaev , Andrew Morton , Linux Kernel Mailing List , clg@fr.ibm.com, alan@lxorguk.ukuu.org.uk, serue@us.ibm.com, arjan@infradead.org, Rik van Riel , Alexey Kuznetsov , Andrey Savochkin , devel@openvz.org, Pavel Emelianov Subject: Re: [RFC][PATCH 1/5] Virtualization/containers: startup References: <43E38BD1.4070707@openvz.org> <43E3915A.2080000@sw.ru> <1138991641.6189.37.camel@localhost.localdomain> <20060203201945.GA18224@kroah.com> <43E3BE66.6050200@watson.ibm.com> <43E615BA.1080402@sw.ru> In-Reply-To: <43E615BA.1080402@sw.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1094 Lines: 32 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/