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: Zachary Amsden <zach@xxxxxxxxxx>
Subject: [Xen-devel] Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal
From: Chris Wright <chrisw@xxxxxxxxxxxx>
Date: Mon, 13 Mar 2006 11:02:34 -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>, 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: Tue, 14 Mar 2006 10:03:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4415BE8F.1080609@xxxxxxxxxx>
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> <4415BE8F.1080609@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
* Zachary Amsden (zach@xxxxxxxxxx) wrote:
> 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.

Replacing a ROM image is easier in terms package management, but still
requires full validation and certification process.  Swapping out the
underlying core is a major change and needs to be re-validated.

thanks,
-chris

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

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