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/
Home Products Support Community News


Re: [Xen-devel] build problems

To: Justin Ferguson <jnferguson@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] build problems
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 29 Dec 2009 09:11:09 +0000
Delivery-date: Tue, 29 Dec 2009 01:11:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <705543260912282224t711d387fk9783d42e8ff6759c@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqIT5Phh/4fwSxcQeKKMNLnitDQFQAF0f6j
Thread-topic: [Xen-devel] build problems
User-agent: Microsoft-Entourage/
On 29/12/2009 06:24, "Justin Ferguson" <jnferguson@xxxxxxxxx> wrote:

> On boot it informs me that I need to use bzImage v2.08 instead of
> v2.04. After some digging around, what it looks like to me is that xen
> at some point was brought up to use v2.08 of the boot protocol and
> this was never backported to the kernel (v2.05 was released
> in 2.6.20). This of course won't work (is there absolutely no one
> actually using the default and supported option?). So I elected to use
> the vmlinux/zImage version and I get the 'error: no multiboot header'
> from grub (for both multiboot & linux directives). I get this for the
> kernel that pulls down from mercurial and the tarball on the website.

I think you are setting up the bootloader incorrectly. What bootloader are
you using? If GRUB, you need a config entry like:
title XEN
  root (hd0,1)
  kernel /boot/xen.gz
  module /boot/vmlinuz-xen <kernel params>
  module /boot/initrd-xen

You get the idea. The main message here is that *Xen* is the kernel, not
Linux dom0. Linux kernel is specified as the first module; initrd as the
second module (if you have an initrd).

You can most assuredly use a 2.6.18 bzImage for dom0 -- Xen knows what to do
with it. Your problem in all cases is I think that you tried to boot dom0
kernel directly, without loading Xen as the kernel from grub's p.o.v.

This type of of question should go to the xen-users list, by the way.

 -- Keir

Xen-devel mailing list

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