From owner-freebsd-virtualization@FreeBSD.ORG Mon May 4 12:27:33 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 5163E1065678 for ; Mon, 4 May 2009 12:27:33 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: from mail.gmx.com (unknown [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id 866738FC1D for ; Mon, 4 May 2009 12:27:32 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: (qmail invoked by alias); 04 May 2009 12:27:30 -0000 Received: from ipa114.43.107.79.tellas.gr (EHLO [169.254.0.4]) [79.107.43.114] by mail.gmx.com (mp-eu005) with SMTP; 04 May 2009 14:27:30 +0200 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX1+KNyVDOa6KHwRjka8QRHPvYmT/SD5jRK9aboWJ6Z Erl42sni4yBflc Message-ID: <49FEDF25.9060901@gmx.com> Date: Mon, 04 May 2009 15:27:17 +0300 From: Nikos Vassiliadis User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Jamie Gritton 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> <49FE5937.3000606@FreeBSD.org> In-Reply-To: <49FE5937.3000606@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.67 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 12:27:33 -0000 Jamie Gritton wrote: > Jails will be able to exist without processes, and in fact with nothing > more than a vimage attached. Ah that's what I was looking for. 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. Yet, VIMAGE is very similar in concept with VRF (http://en.wikipedia.org/wiki/VRF) and I think FreeBSD will look very promising in router-like applications:) Maybe there are applications of VIMAGE which haven't been considered by its developers. Time will tell... Nikos