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

Re: [Xen-devel] [Q]Which part of Xen is in slated for 2.6.23 kernel rele

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Q]Which part of Xen is in slated for 2.6.23 kernel release?
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Sat, 21 Jul 2007 19:24:40 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 21 Jul 2007 11:22:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2C7BDAE.B339%keir@xxxxxxxxxxxxx>
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: <6bc632150707210421q1397d529n5945ed943304b815@xxxxxxxxxxxxxx> <C2C7BDAE.B339%keir@xxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Sat, Jul 21, 2007 at 01:42:06PM +0100, Keir Fraser wrote:
> 
> 
> 
> On 21/7/07 12:21, "pradeep singh rautela" <rautelap@xxxxxxxxx> wrote:
> 
> >> The scope of the patches is domU guest support. Vanilla linux 2.6.23 will
> >> not support running as dom0 (Jeremy is working on this for a future Linux
> >> release). Nor does it contain the hypervisor code itself -- you have to
> >> obtain the Xen hypervisor separately from the kernel sources.
> > 
> > Great!!!
> > So this means 2.6.23 vanilla kernel can be compiled as a domU natively, 
> > right?
> 
> Yes. In fact the paravirt_ops framework means that you can build a single
> kernel that will work natively or on Xen (or on VMware or lguest or ...).

I thought that with this initial merge, we stll had to build separate 
images for bare metal vs Xen paravirt because of the way Linux uses 
the bzImage, while Xen is in ELF format ? Or has this bootup difference
already been resolved ?


Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

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