From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: Device Namespaces Date: Mon, 30 Sep 2013 08:37:19 -0700 Message-ID: <1380555439.2161.5.camel@dabdike.int.hansenpartnership.com> References: <8761udlu0d.fsf@xmission.com> <871u4yddg4.fsf@xmission.com> <87bo3gshz5.fsf_-_@xmission.com> <20130926053320.GB3725@kroah.com> <20130926135604.GA16624@kroah.com> <20130926170757.GA9345@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130926170757.GA9345-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Greg Kroah-Hartman Cc: Linux Containers , Kay Sievers , Stephane Graber , Andy Lutomirski , "Eric W. Biederman" , lxc-devel , mhw , devel List-Id: containers.vger.kernel.org On Thu, 2013-09-26 at 10:07 -0700, Greg Kroah-Hartman wrote: > On Thu, Sep 26, 2013 at 08:01:31PM +0300, Janne Karhunen wrote: > > That being said, our wish would be to support any combination of > > OS's and frankly, I'd be slightly annoyed to tell the customer that > > they can't do two Androids or we magically run out of bits. > > If you want to support "any" combination of operating systems, then use > a hypervisor, that's what they are there for :) No that's not quite the right way to think about it: The correct statement is only use a hypervisor if you need different kernels. With Windows, it happens to be true that you need a different kernel for each different OS version. However; with Linux, thanks to strong ABI backwards compatibility, you mostly don't. The way OpenVZ works today is that it installs a modified kernel which can then bring up every Linux OS in a separate container. Our use case is the hosters that give you root login to a virtual private server and allow you to upgrade it on your own. The reason for using a container rather than a hypervisor is the old density and elasticity one: 3x the density (i.e. 1/3 the overhead cost to the hoster) and the boot only needs to start at init, not bring up of virtual hardware and booting a second kernel. James