From owner-freebsd-current@FreeBSD.ORG Tue Feb 26 17:23:33 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ED7F10656C8 for ; Tue, 26 Feb 2008 17:23:33 +0000 (UTC) (envelope-from bazerka@beardz.net) Received: from svr03-temp.btshosting.co.uk (svr03-temp.btshosting.co.uk [87.117.208.48]) by mx1.freebsd.org (Postfix) with ESMTP id E5DA513C478 for ; Tue, 26 Feb 2008 17:23:32 +0000 (UTC) (envelope-from bazerka@beardz.net) Received: from [192.168.1.65] (host86-139-98-128.range86-139.btcentralplus.com [86.139.98.128]) (authenticated bits=0) by svr03-temp.btshosting.co.uk (8.14.1/8.14.1) with ESMTP id m1QH8Db8006408; Tue, 26 Feb 2008 17:08:14 GMT (envelope-from bazerka@beardz.net) Message-ID: <47C44777.6060404@beardz.net> Date: Tue, 26 Feb 2008 17:08:07 +0000 From: Jase Thew User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Julian Elischer References: <47C44420.6050009@elischer.org> In-Reply-To: <47C44420.6050009@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.92.1, clamav-milter version 0.92.1 on 87.117.208.49 X-Virus-Status: Clean Cc: FreeBSD Current Subject: Re: why vimage? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bazerka@beardz.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 17:23:33 -0000 Julian Elischer wrote: > some people have asked me why I would want vimage.. > The answer is because it allows you to do lots of things easily > that are hard to do normally. > > I can give a very simple example of something you can do trivially on > vimage: > > Make three virtual machines on yhour laptop: > The base machine and two others. > Have the first 'other' machine be assigned an IP address on > your HOME LAN. > have the second virtual machine have an IP adddress on > your WORK LAN. > use the base machine to run encrypted tunnels from where-ever > you happen to be to your work and home.. when you put the laptop to > sleep (assuming the tcp sessions are quiescent (no keepalives)) > then when you wake it up say an hour later.. as soon as the base > machine has an IP address.. viola, your session on the virtual > machines are still alive. > > there are SO MANY things you can do with this.. and the framework > allows us to proceed with more virtualisation including > separate PID spaces or processor quotas etc. > > BUT the framework will never get the mindshare needed unless people > start playing with it. > vimage will be a boon for replacing full system jails. I think the more important question is: why people *wouldn't* want vimage incorporated into the tree? The benefits it offers are pretty vast and from what I can see, there are hardly any disadvantages ( although I'm willing to be enlightened if there are any major gotchas ). Jase.