WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interfac

To: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal
From: Joshua LeVasseur <jtl@xxxxxxxxxx>
Date: Mon, 13 Mar 2006 19:56:04 +0100
Cc: Zachary Amsden <zach@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Pratap Subrahmanyam <pratap@xxxxxxxxxx>, Wim Coekaerts <wim.coekaerts@xxxxxxxxxx>, Chris Wright <chrisw@xxxxxxxx>, Jack Lo <jlo@xxxxxxxxxx>, Dan Hecht <dhecht@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>, Christopher Li <chrisl@xxxxxxxxxx>, Virtualization Mailing List <virtualization@xxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxx>, Anne Holler <anne@xxxxxxxxxx>, Jyothy Reddy <jreddy@xxxxxxxxxx>, Kip Macy <kmacy@xxxxxxxxxxx>, Ky Srinivasan <ksrinivasan@xxxxxxxxxx>, Leendert van Doorn <leendert@xxxxxxxxxxxxxx>, Dan Arai <arai@xxxxxxxxxx>
Delivery-date: Tue, 14 Mar 2006 10:03:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1142275365.3023.44.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200603131758.k2DHwQM7005618@xxxxxxxxxxxxxxxxxxx> <1142273346.3023.38.camel@xxxxxxxxxxxxxxxxxxxxx> <4415B857.9010902@xxxxxxxxxx> <1142274398.3023.40.camel@xxxxxxxxxxxxxxxxxxxxx> <4415BA4F.3040307@xxxxxxxxxx> <1142275365.3023.44.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On Mar 13, 2006, at 19:42, Arjan van de Ven wrote:

On Mon, 2006-03-13 at 10:30 -0800, Zachary Amsden wrote:
 and gives hypervisors room to grow while maintaining
binary compatibility with already released kernels.

that I buy for binary only hypervisors. But in an open source world I'll
buy this a LOT less as being relevant.



Binary compatibility to Linux is pretty important for applications. Even though Apache is open source, I don't want to recompile it for every new Linux kernel. Fortunately I don't have to, because glibc abstracts the Linux kernel interface. Consider VMI in the same role as glibc -- when the hypervisor changes, VMI maintains compatibility with your pre-existing infrastructure, while letting you have some of the benefits of the new hypervisor. The upgrade and recompile game can quickly end in a stalemate when you have packages with conflicting dependencies (one package requires the old version, and the other package requires the new version).

Josh


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>