[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal
- To: Joshua LeVasseur <jtl@xxxxxxxxxx>
- From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
- Date: Thu, 16 Mar 2006 19:52:18 +0100 (MET)
- 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>, Leendert van Doorn <leendert@xxxxxxxxxxxxxx>, Anne Holler <anne@xxxxxxxxxx>, Jyothy Reddy <jreddy@xxxxxxxxxx>, Kip Macy <kmacy@xxxxxxxxxxx>, Ky Srinivasan <ksrinivasan@xxxxxxxxxx>, Dan Arai <arai@xxxxxxxxxx>, Arjan van de Ven <arjan@xxxxxxxxxxxxx>
- Delivery-date: Fri, 17 Mar 2006 10:57:15 +0000
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
>> > 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,
VMI = kernel code (AFAIU)
I would rather like a user-space-based compat layer.
Xen-devel mailing list