From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Xen Paravirt Date: Wed, 18 Jul 2007 22:04:01 -0700 Message-ID: <469EF0C1.80907@goop.org> References: <27c823430707181545y2e906307rfd88bd81ee9d4274@mail.gmail.com> <469EA658.5070106@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Nate Carlson Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Nate Carlson wrote: > On Wed, 18 Jul 2007, Jeremy Fitzhardinge wrote: >> If you build the kernel with CONFIG_PARAVIRT=y, CONFIG_XEN=y and >> enable the Xen console, block and net devices (they will default =y), >> then you should be able to use the resulting kernel with an existing >> Xen installation (it will also boot native). Unfortunately you can't >> use the same actual kernel image file in both cases, but you can use >> the same modules. > > Just curious, will that change? :) Yeah, it's a work in progress. I have some test patches to extend the bzImage format to contain ELF notes, and a corresponding Xen patch to add a new file format for the domain builder. But its a bit up-in-the-air because nobody has agreed to the bzImage format changes, and its all a bit subtle to make sure it keeps working with a wide range of fairly poorly implemented bootloaders. J