From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: [Q]Which part of Xen is in slated for 2.6.23
	kernel release?
Date: Sat, 21 Jul 2007 19:38:40 +0100
Message-ID: <C2C81140.B352%keir@xensource.com>
References: <20070721182440.GA27107@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20070721182440.GA27107@redhat.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 21/7/07 19:24, "Daniel P. Berrange" <berrange@redhat.com> wrote:

>> 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 ?

Actually yes, it's still in progress. So currently it is true that you can
target native or Xen from a single *build*, but you then take different
image files (vmlinux vs bzImage).

 -- Keir