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: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] build problems
From: Justin Ferguson <jnferguson@xxxxxxxxx>
Date: Tue, 29 Dec 2009 05:29:20 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 29 Dec 2009 04:29:44 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=N22B5iQoyWA/D9pq5CivydLhJoCs5JsVE0xZ+rn9hd4=; b=otezTY5oJWuQNGXxeSkmpGC9wX9dDDqJ1G86GHXZPhFhTHmUe9dqcGoYJka8FMhK+B R7ABHl54X51p2hF/elOS4aIAqYXqeBwzszSOCFzXZq/8B0e15Q318FdwSLrEoU24KL7+ 5tYB+OjEY1kTASZwv0a27Y2FDLyEXuuZH+5i8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=HnGUjDA2aGma6uu2nxWXeczMCwyfxfZkuhpz9fQIP8EtdrdQalsF75b4i+X0Zb/f5h BHsvWzJgSR6zimMt0PqfPNMcQ067MJQz6gE3HHMemhpnbynf/ZuUynm3WLejdwsXtdGh Es9Z+3uo0dtIuLPN5mnTA6HGQVjZWqjFuaDjs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1262081968.31374.9.camel@xxxxxxxxxxxxxxxxxxxxx>
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>
References: <C75F782D.53D9%keir.fraser@xxxxxxxxxxxxx> <1262081277.31374.2.camel@xxxxxxxxxxxxxxxxxxxxx> <705543260912290210j60a8709by9ef9874d63eec270@xxxxxxxxxxxxxx> <1262081968.31374.9.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I apologize in advance as my terminology on the various linux kernel
compression formats is not the best (up until today I thought bzImage
was just a bzip'd copy of the elf image, and the documentation here
uses a lot of conflicting terminology)-- I am not positive if it is
zImage or what format it is (other than I know it is not bzImage),

jf@theory:/boot$ file vmlinux ; zcat vmlinuz | file -
vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linked, stripped
/dev/stdin: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linked, stripped

(I changed both file names to make them easy to type with tab
completion as ive been doing a lot of rebooting as of late)

> The kernel you use must be the toplevel vmlinux ELF file, optionally
> stripped and optionally gzip compressed. This is not the same as a
> zImage which is a format similar to to bzImage but not able to cope with
> such large images (it is effectively obsolete).

When I attempt to boot either of these kernels from the command line,
I get the (presumably grub due to the lack of verbosity) invalid magic
error.  Where I am unclear on grub is whether I am supposed to be
using 'multiboot' or 'linux' as the operand (to replace 'kernel'), the
bzimage i needed multiboot, but none of the images ive created have
contained a (findable) multiboot header (per mbchk),

That said I may be making things unnecessarily stupid on myself by
using some new-fangled version of grub (that shipped with the distro).
Regardless of whether I am doing something wrong with grub, one of the
resulting images should boot, however all are returning the magic

> I think there is a target in the 2.6.18-xen tree which will perform this
> strip and compress step for you but I don't recall what it is, it might
> be the "vmlinuz" target although note that people often rename whatever
> image they have built to that name so if you find one lying around it
> isn't necessarily in any particular format.

Well a make kernels leaves you with the top level image necessary (or
other ones in the arch directories). A full make world/make install
installs a bzImage. The implication here of course is that the default
image installed from a make install is the bzImage that cannot
possibly work. (v2.04-v2.08 thing)

> If you need to post again please include the exact grub config file you
> are using and the precise error messages rather than paraphrasing.

So, the grub.cfg I have at the moment contains the entry from the last
make world/make install, since then I've attempted to boot the top
level images on the command line as described. To satify you're
request, the relevant entry is as follows:

menuentry "xen" {
        multiboot /boot/xen-3.4.gz dom0_mem=512M
        module /boot/vmlinuz-2.6.18-xen root=/dev/sda5 ro
        module /boot/initrd-2.6-xen.img

I'm not attempting to clutter the dev list with user list type things,
but I'm fairly certain there is a bug here.


Xen-devel mailing list

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