From owner-freebsd-virtualization@FreeBSD.ORG Mon May 4 02:55:55 2009 Return-Path: Delivered-To: virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B35E9106566B for ; Mon, 4 May 2009 02:55:55 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from gritton.org (gritton.org [161.58.222.4]) by mx1.freebsd.org (Postfix) with ESMTP id 77A4A8FC08 for ; Mon, 4 May 2009 02:55:55 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from glorfindel.gritton.org (c-76-27-80-223.hsd1.ut.comcast.net [76.27.80.223]) (authenticated bits=0) by gritton.org (8.13.6.20060614/8.13.6) with ESMTP id n442trPv023146; Sun, 3 May 2009 20:55:54 -0600 (MDT) Message-ID: <49FE5937.3000606@FreeBSD.org> Date: Sun, 03 May 2009 20:55:51 -0600 From: Jamie Gritton User-Agent: Thunderbird 2.0.0.19 (X11/20090220) MIME-Version: 1.0 To: Nikos Vassiliadis References: <20090413.220932.74699777.sthaug@nethelp.no> <49E57076.7040509@elischer.org> <20090424202923.235660@gmx.net> <200904242249.27640.zec@icir.org> <20090425133006.311010@gmx.net> <20090502131259.31160@gmx.net> <49FC78DA.2010201@elischer.org> <20090503103244.44760@gmx.net> <49FDD9B9.7090403@elischer.org> <49FDDD02.3090803@gmx.com> In-Reply-To: <49FDDD02.3090803@gmx.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.94.2/9321/Sun May 3 16:33:47 2009 on gritton.org X-Virus-Status: Clean X-Mailman-Approved-At: Mon, 04 May 2009 03:59:52 +0000 Cc: virtualization@FreeBSD.org Subject: Re: VIMAGE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2009 02:55:55 -0000 Nikos Vassiliadis wrote: > Julian Elischer wrote: >> Peter Cornelius wrote: >>> Re... >>> >>>> The situation is that right now jail and vimage are >>>> orthogonal (ish) however in the future, >>>> vimage will become a set of options on jail. >>> >>> Ah. SO it probably is kinda useless to try and stick a couple of >>> jails 'inside' a vimage. >> >> no you will be able to nest jails. >> some of them may have the vimage options and some may not. > > What about vimages without jails? > I can imagine some applications of VIMAGE which completely > lack user-space processing. If I recall correctly a jail > exists as far there is at least one process associated with > it. Would that be feasible? > Having a vimage with no processes? Jails will be able to exist without processes, and in fact with nothing more than a vimage attached. But much of vimage only makes sense in conjunction with processes - a process attached to a vimage can see that vimage's network interfaces. There are still things like routing that work independent of processes I suppose, but it seems to me much what a vimage does is provide the network stack to the processes it's tied to. - Jamie