[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86: Support booting a bzImage format domain 0 kernel


  • To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  • From: "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@xxxxxx>
  • Date: Thu, 22 Jan 2009 16:15:31 +0100
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 22 Jan 2009 07:17:05 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Am Donnerstag, den 22.01.2009, 13:10 +0000 schrieb Ian Campbell:
> On Thu, 2009-01-22 at 13:18 +0100, Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ] wrote:
> > Hello Ian,
> > 
> > Am Donnerstag, den 22.01.2009, 11:53 +0100 schrieb Ian Campbell:
> > --8<--
> > > x86: Support booting a bzImage format domain 0 kernel.
> > > 
> > > This requires a bzImage v2.08 or later kernel.
> > > 
> > > xen/common/inflate.c is taken unmodified from Linux v2.6.28.
> > > 
> > > Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
> > --8<--
> > 
> > i bow before you, this is awesome. :oD
> 
> Thanks.

Another step forward to get the one kernel that rules them all ;o)

> > It applies to 3.3.1 with a few offsets but no fuzz!
> > 
> > I'll build xen 3.3.1, test and report back :o)

It fails to build as the bzimage.h file is missing (log attached).
I also didn't found one in unstable and vanilla 2.6.28 sources?!

> 
> Note that you will need a recent pvops dom0 kernel from Jeremy's patch
> queue (see http://wiki.xensource.com/xenwiki/XenParavirtOps for details)
> in order to get dom0 and v2.08 bzImage support in the same image.

Yup, already half down the road to rebuild that beast with Jeremy's last
commit.

> In particular the 2.6.18-xen tree is not suitable.
> 
> Ian.
> 

Attachment: xen-3.3.1-0.6.0-i686-build.log
Description: Text Data

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.