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: Zachary Amsden <zach@xxxxxxxxxx>
Date: Mon, 13 Mar 2006 10:48:47 -0800
Cc: Andrew Morton <akpm@xxxxxxxx>, Joshua LeVasseur <jtl@xxxxxxxxxx>, 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:01:55 +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
User-agent: Thunderbird 1.5 (X11/20051201)
Arjan van de Ven wrote:

makes debugging and development easier,

that I don't buy; a fixed interface tends to make debugging harder not
easier since you can't change it to add more information

This we find to be quite true. Now, you can use a VMI kernel, make changes to it, run it on native hardware, and be confident that it will run properly in a VM as well. And you can develop in a VM, with confidence that you can run on native hardware. You can even replace the entire "ROM" image with your own custom debugging image to add any type of debugging or performance monitoring facility you want - and you have some very, very interesting hook points into the kernel that make that task much more achievable.


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

This is not about the open source versus the closed source world. It is about the real world, where customers want to make as few changes as possible to a working and already deployed system. If they have to recompile a kernel just to get their system to run again, that is a pain point that is easily avoided.


Zach

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

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