Syslinux - Nov 2006 - booting Xen hypervisor

Hello,

I'm having trouble PXE booting the Xen hypervisor kernel as follows:

PXELINUX 3.31 0x4518b206  Copyright (C) 1994-2005 H. Peter Anvin
UNDI data segment at:   00094FC0
UNDI data segment size: 4A30
UNDI code segment at:   000999F0
UNDI code segment size: 44E4
PXE entry point found (we hope) at 999F:00D6
My IP address seems to be 0A000063 10.0.0.99
ip=10.0.0.99:10.0.1.1:10.0.0.1:255.0.0.0
TFTP prefix: /
Trying to load: pxelinux.cfg/01-00-0d-60-d5-d6-3b
COM32 Multiboot loader v0.2.  Copyright (C) 2005-2006 Tim Deegan.
Kernel: boot/xen.gz nosmp noacpi
Loading boot/xen.gz.......
Module: boot/res-1-kernel ramdisk_size=131072 ramdisk_blocksize=1024
console=tty
S0 apm=off id=1 qrm=10.0.1.1 ip=10.0.0.99:10.0.1.1:10.0.0.1:255.0.0.0
BOOTIF=00:
0d:60:d5:d6:3b
Loading boot/res-1-kernel........................
Module: boot/res-1-initrd.img
Loading
boot/res-1-initrd.img...................................................
................................................................................
................................................................................
......................................
Booting: MBI=0x000100a8, entry=0x00100000

The system hangs here and does nothing

I found some other posts on this list which seem to describe a similar
problem.

I'm using an Intel Xeon architecture and Fedora Core 6 with gcc-4.1.1-30
and glibc-2.5-3

my pxelinux.cfg file is as follows:

default xen

label xen
 kernel pxelinux/com32/modules/mboot.c32
 append boot/xen.gz nosmp noacpi --- boot/res-1-kernel
ramdisk_size=131072 ramdisk_blocksize=1024 console=ttyS0 apm=off id=1
qrm=10.0.1.1 ip=10.0.0.99:10.0.1.1:10.0.0.1:255.0.0.0
BOOTIF=00:0d:60:d5:d6:3b --- boot/res-1-initrd.img
 ipappend 3

Let me know if any other information is needed.

Thanks,
-- 
#################
 #               #
  #################
 #     <(o)>     ##
################# #
# Peter Schobel # #
#  1iopen.net   ##
#################

Hi, 
> label xen
>  kernel pxelinux/com32/modules/mboot.c32
>  append boot/xen.gz nosmp noacpi --- boot/res-1-kernel
> ramdisk_size=131072 ramdisk_blocksize=1024 console=ttyS0 apm=off id=1
> qrm=10.0.1.1 ip=10.0.0.99:10.0.1.1:10.0.0.1:255.0.0.0
> BOOTIF=00:0d:60:d5:d6:3b --- boot/res-1-initrd.img
>  ipappend 3
The IPAPPEND flag won't work with Xen; it will just add things to the
end of the mboot.c32 command line, which will be translated into
command-line arguments to the initrd image (which should be ignored by
Xen).  It clashes with the explicit IP information you're supplying anyway.

If you're using a serial line, you need to tell Xen where its console
is, e.g. for a serial console add "com1=115200,8n1 console=com1" after
"boot/xen.gz".  To explicitly request the vga console, use
"console=tty".

Cheers,

Tim.

-- 
Tim Deegan                           (My opinions, not the University's)
Systems Research Group
University of Cambridge Computer Laboratory

Op 25-11-2006 om 13:31 schreef John Smith:
> > Does that mean that xen works with pxelinux?
> > 
> > If yes, could the working setup be posted here?
> 
> My working config :

Now on the syslinux wiki.


Thanks
Geert Stappers