From: Ian Campbell <Ian.Campbell@citrix.com>
To: Justin Ferguson <jnferguson@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: build problems
Date: Tue, 29 Dec 2009 10:19:28 +0000 [thread overview]
Message-ID: <1262081968.31374.9.camel@localhost.localdomain> (raw)
In-Reply-To: <705543260912290210j60a8709by9ef9874d63eec270@mail.gmail.com>
On Tue, 2009-12-29 at 10:10 +0000, Justin Ferguson wrote:
> >> You can most assuredly use a 2.6.18 bzImage for dom0 -- Xen knows what
> >> to do with it.
> >
> > Unless someone backported the v2.08 bzImage format extensions (which I
> > don't think is the case) then you cannot boot a 2.6.18 bzImage under
> > Xen, that support relies on newer fields in the header. IIRC those
> > patches went into 2.6.27 upstream, although e.g. Debian backported them
> > to their 2.6.26 kernel.
> >
> > For 2.6.18 I think you still need to use the old compressed-ELF style
> > kernels.
>
> Which, may be a problem with my grub config-- but i dont think it is,
> I can't seem to get grub 2 to boot the resultant vmlinux/zImage, it
> just likes to tell me its missing the magic number-- which I'm
> guessing, and my knowledge gets hazy here, is a result of it not being
> a multiboot compatible image?
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).
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.
A correct 2.6.18-xen kernel should respond to the file command like
this: (I happened to have a 2.6.26-xen image hanging around, the output
should be the same for 2.6.18-xen)
$ file /boot/vmlinuz-2.6.26-2-xen-amd64
/boot/vmlinuz-2.6.26-2-xen-amd64: gzip compressed data, from Unix, last modified: Thu Aug 20 01:36:37 2009, max compression
$ zcat /boot/vmlinuz-2.6.26-2-xen-amd64 | file -
zcat /boot/vmlinuz-2.6.26-2-xen-amd64 | file -
/dev/stdin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
32 bit kernels will be similar.
The grub examples Keir gave are correct, you just need to be careful
about the kernel image you use.
If you need to post again please include the exact grub config file you
are using and the precise error messages rather than paraphrasing.
Ian.
next prev parent reply other threads:[~2009-12-29 10:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 6:24 build problems Justin Ferguson
2009-12-29 9:11 ` Keir Fraser
2009-12-29 10:07 ` Ian Campbell
2009-12-29 10:10 ` Justin Ferguson
2009-12-29 10:19 ` Ian Campbell [this message]
2009-12-29 12:29 ` Justin Ferguson
2009-12-29 13:13 ` Ian Campbell
2009-12-30 9:27 ` Justin Ferguson
-- strict thread matches above, loose matches on Subject: below --
2024-06-03 23:34 Build problems Ananth, Rajesh
2024-06-04 20:28 ` Patrick Williams
2009-01-27 12:25 Paolo Cremonese
2009-01-27 13:18 ` Charlton, John
2009-01-27 13:35 ` Marco Cavallini
2009-01-28 9:49 ` Paolo Cremonese
2009-01-28 10:03 ` Marco Cavallini
2009-01-29 11:14 ` Paolo Cremonese
2009-01-29 12:35 ` Yuri Bushmelev
2009-01-30 16:33 ` Marco Cavallini
2009-02-02 14:57 ` Paolo Cremonese
2009-02-02 15:17 ` Ihar Hrachyshka
2009-02-02 16:46 ` Philip Balister
2009-02-02 16:13 ` Marco Cavallini
2009-02-04 9:27 ` Paolo Cremonese
2009-02-04 11:29 ` Koen Kooi
2009-02-04 15:48 ` Paolo Cremonese
2009-02-04 17:47 ` Marcin Juszkiewicz
2009-01-28 10:04 ` Elena of Valhalla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1262081968.31374.9.camel@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=jnferguson@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.