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

Re: [Xen-devel] Invalid or unsupported executable format, or is it a reiserfs problem?

I have reinstalled that machine with a ext3 /boot partition and a reiserfs / partition

/dev/hda1  /boot (ext3)
/dev/hda2 swap
/dev/hda4 /  (reiserfs)

Installation from source

tar xvf xen-2.0.4.tgz
cd xen-2.0
make world
make install
mkinitrd -o /boot/initrd.img-2.6.10-xen0 2.6.10-xen0

Edit menu.lst in /boot/grub
add serial support for grub:
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
terminal --timeout=5 serial console

Entry for Xen:
title Xen-2.0
root (hd0,0) # also tried without
kernel /xen.gz dom0_mem=64000
module /vmlinux-2.6.10-xen0 root=/dev/hda4 ro console=tty0 console=ttyS0,115200n8
module /initrd.img-2.6.10-xen0 #also tried without

Connect to another host with null modem cable.
start minicom and  configure with serial parameters to 115200, parity=no, data="" stop=1
hardware flow control = yes
software flow control = no
terminal = VT102
backspace sends BS

The xen kernel does not boot
I don't see anything on the terminal from grub or xenlinux  (I do see the output when booting the normal debian kernel)
I am lost !

Does anybody know how to go on from here or do I have no other choice then to download fedora core 3 and try it with that distribution?
Thanks in advance for any help.


Filip Sergeys

On Thu, 2005-02-17 at 16:32, Steven Hand wrote:
> On Thu, 2005-02-17 at 14:56, Steven Hand wrote:
>     > Our newly build xen kernel does not boot. The error message is : Invalid
>     > or unsupported executable format. 
>     > 
>     > I have build xen from the xen-2.0.4 source (make world, make install) on
>     > a debian sarge system. 
>     > I have not changed any of the kernel configurations, I did make an
>     > initrd image. 
>     > The entry in my menu.lst is : 
>     > 
>     > title           Debian GNU/Linux, kernel 2.6.10-xen0 
>     > root            (hd0,0) # I also tried without this line. 
>     > kernel          /boot/xen.gz dom0_mem=64000 
>     > module          /boot/vmlinuz-2.6.10-xen0 root=/dev/hda1 ro 
>     > module          /boot/initrd.img-2.6.10-xen0 # Also tried without this
>     > line 
>     > 
>     > The server's / (/boot) partition is reiserfs. I wonder if this is the
>     > problem? I found messages saying that it doesn't work with reiserfs and
>     > others that say it should work. What is the final answer? 
>     > Looking in the kernel config file: reiserfs is build into the kernel,
>     > not as a module. 
>     What does `file /boot/xen.gz' say? 
> /boot/xen.gz: gzip compressed data, from Unix, max compression
>     What does `cat /boot/xen.gz | gunzip -c | file -` say? 
> /dev/stdin: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> statically linked, stripped

Ok, that looks good. 

>     > As a side note: the standard debian 2.6.8-2 kernel works perfectly. 

Hmm: what is the menu.lst you use for that? In particular, is the
kernel you boot in the same directory as xen.gz? 

What's the overall makeup of your partitions + filesystems in the
machine? I'm guessing /dev/hda1 is { /boot, reiserfs } -- what 
about the rest of the system? 

> Thinking ahead, suppose reiserfs has to be dropped, will it suffice to
> just convert the /boot partition to ext3 or does the entire / partition
> need to be converted?

Well ideally it should all "just work" even with reiserfs as /boot. 

How did you get xen.gz onto /boot? Did you copy it from an ext2/3 
partition? There seems to be something weird about reiserfs and 
grub involving the "-notail" mount option... 



SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list
* System Engineer, Verzekeringen NV *
* www.verzekeringen.be              *
* Oostkaai 23 B-2170 Merksem        *
* 03/6416673 - 0477/340942          *



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