Mailing List Archive

Eric Nicholson wrote:
>
> I noticed that the grub.conf file now has a kernel line referencing the
> "/xen.gz-2.6.18-8.1.3el5" with a seperate module line for
> "vmlinuz-2.6.18-8.1.3el5xen"
>
> Does the isolinux.cfg file support the "module" line?
>
> It seems like something needs to be added to the isolinux.cfg to make
> this work now.
>

To load Xen-based kernels you have to use the SYSLINUX multiboot module
-- mboot.c32. See the mailing list archives
(http://syslinux.zytor.com/archives), or there might be something on the
wiki (http://syslinux.zytor.com/wiki).

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

On 5/9/07, H. Peter Anvin <hpa@zytor.com> wrote:
> Eric Nicholson wrote:
> >
> > I noticed that the grub.conf file now has a kernel line referencing the
> > "/xen.gz-2.6.18-8.1.3el5" with a seperate module line for
> > "vmlinuz-2.6.18-8.1.3el5xen"
> >
> > Does the isolinux.cfg file support the "module" line?
> >
> > It seems like something needs to be added to the isolinux.cfg to make
> > this work now.
> >
>
> To load Xen-based kernels you have to use the SYSLINUX multiboot module
> -- mboot.c32. See the mailing list archives
> (http://syslinux.zytor.com/archives), or there might be something on the
> wiki (http://syslinux.zytor.com/wiki).
>
> -hpa

Thanks for the help, I am now getting much further. However, I now
get the following message:

kernel panic: not syncing: VFS: Unable to mount root fs on unknown-block (1,0)

Above this message I can see a message saying that it is loading the
ramdisk filesystem..done , and then a message that says:

EXT2-fs block size to small for device
grow_buffers: out of range block...

The rest scrolls pretty quick.

I have searched through the archives listed above and have been trying
different options but still no luck in getting past the panic.

Here is a copy of what my isolinux.cfg looks like:

default linux
display message
prompt 1
timeout 600
label linux
kernel mboot.c32
append xen.gz nosmp noacpi --- vmlinuz ramdisk=30720 root=/dev/ram0
--- initrd.img

The initrd.img is an ext2 filesystem. Is there a particular block size
to be used to create the ext2 fs for the ramdisk to load properly now
and mount?

Any ideas on what I'm missing or need to add for mounting the ramdisk image?



Thanks again,
Eric

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

> On 5/9/07, H. Peter Anvin <hpa@zytor.com> wrote:
> >
> > To load Xen-based kernels you have to use the SYSLINUX multiboot module
> > -- mboot.c32. See the mailing list archives
> > (http://syslinux.zytor.com/archives), or there might be something on the
> > wiki (http://syslinux.zytor.com/wiki).
> >
> > -hpa
>
> Thanks for the help, I am now getting much further.

Updates on http://syslinux.zytor.com/wiki/index.php/Xen are very welcome.


> However, I now get the following message:
>
> kernel panic: not syncing: VFS: Unable to mount root fs on unknown-block (1,0)
<snip/>
> I have searched through the archives listed above and have been trying
> different options but still no luck in getting past the panic.

The syslinux archive is about the syslinux bootloader family.
Booted kernels that can't access a root filesystem
could be a "syslinux issue",
but could be also outside the scoop of syslinux.


> Here is a copy of what my isolinux.cfg looks like:
<snip/>
> kernel mboot.c32
> append xen.gz nosmp noacpi --- vmlinuz ramdisk=30720 root=/dev/ram0 --- initrd.img
>
> The initrd.img is an ext2 filesystem. Is there a particular block size
> to be used to create the ext2 fs for the ramdisk to load properly now
> and mount?
>
> Any ideas on what I'm missing or need to add for mounting the ramdisk image?

Information that might help:

There was / is much evolution in the initrd area.


My advice is to
reread up-to-date documentation of the initrd tools that you are using.


> Thanks again,
> Eric


Looking forward for feedback
Geert Stappers

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

On 5/11/07, Geert Stappers <stappers@stappers.nl> wrote:
> > On 5/9/07, H. Peter Anvin <hpa@zytor.com> wrote:
> > >
> > > To load Xen-based kernels you have to use the SYSLINUX multiboot module
> > > -- mboot.c32. See the mailing list archives
> > > (http://syslinux.zytor.com/archives), or there might be something on the
> > > wiki (http://syslinux.zytor.com/wiki).
> > >
> > > -hpa
> >
> > Thanks for the help, I am now getting much further.
>
> Updates on http://syslinux.zytor.com/wiki/index.php/Xen are very welcome.
>
>
> > However, I now get the following message:
> >
> > kernel panic: not syncing: VFS: Unable to mount root fs on unknown-block (1,0)
> <snip/>
> > I have searched through the archives listed above and have been trying
> > different options but still no luck in getting past the panic.
>
> The syslinux archive is about the syslinux bootloader family.
> Booted kernels that can't access a root filesystem
> could be a "syslinux issue",
> but could be also outside the scoop of syslinux.
>
>
> > Here is a copy of what my isolinux.cfg looks like:
> <snip/>
> > kernel mboot.c32
> > append xen.gz nosmp noacpi --- vmlinuz ramdisk=30720 root=/dev/ram0 --- initrd.img
> >
> > The initrd.img is an ext2 filesystem. Is there a particular block size
> > to be used to create the ext2 fs for the ramdisk to load properly now
> > and mount?
> >
> > Any ideas on what I'm missing or need to add for mounting the ramdisk image?
>
> Information that might help:
>
> There was / is much evolution in the initrd area.
>
>
> My advice is to
> reread up-to-date documentation of the initrd tools that you are using.
>
>
> > Thanks again,
> > Eric
>
>
> Looking forward for feedback
> Geert Stappers

Thanks for the information. I finally have it working.

The mboot.c32 fixed the problem with booting the multiple kernels,
however, I noticed that mboot does not like kernel names with the
version extension
ie: kernel /xen.gz-2.6.18-8.1.3.el5

Once I modified the isolinux.cfg to
kernel /xen.gz
It went passed that point.

The next problem was failing to mount of the root file system. The key
error message I found there was
"EXT2-fs block size to small for device"

It appears under Centos 5 and RedHat Enterprise Linux 5 there is a bug
with the EXT2-fs default block size being recognized. Adding the
following line to the kernel append fixed this:

ramdisk_blocksize=1024

I imagine that this is a bug in the particular kernel version and not
limited to the Linux Distributions listed above.

So my isolinux.cfg now looks like:

label linux
kernel mboot.c32
append xen.gz nosmp noacpi --- vmlinuz ramdisk=30720
ramdisk_blocksize=1024 root=/dev/ram0
--- initrd.img

Here is a link to the page where I found this bug report for the
EXT2-fs ramdisk_blocksize:

http://wiki.systemimager.org/index.php/Troubleshooting#Ramdisk_too_small.3F_Getting_errors.3F

I can provide or post these updates on the wiki if you would prefer.

Thank you for all your help.
Eric Nicholson

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Op 11-05-2007 om 12:25 schreef Eric Nicholson:
> On 5/11/07, Geert Stappers <stappers@stappers.nl> wrote:
> >
> > My advice is to
> > reread up-to-date documentation of the initrd tools that you are using.
> >
> >
> >
> > Looking forward for feedback
> > Geert Stappers
>
> Thanks for the information. I finally have it working.
>
> The mboot.c32 fixed the problem with booting the multiple kernels,
> however, I noticed that mboot does not like kernel names with the
> version extension
> ie: kernel /xen.gz-2.6.18-8.1.3.el5
>
> Once I modified the isolinux.cfg to
> kernel /xen.gz
> It went passed that point.
>
> The next problem was failing to mount of the root file system. The key
> error message I found there was
> "EXT2-fs block size to small for device"
>
> It appears under Centos 5 and RedHat Enterprise Linux 5 there is a bug
> with the EXT2-fs default block size being recognized. Adding the
> following line to the kernel append fixed this:
>
> ramdisk_blocksize=1024
>
> I imagine that this is a bug in the particular kernel version and not
> limited to the Linux Distributions listed above.
>
> So my isolinux.cfg now looks like:
>
> label linux
> kernel mboot.c32
> append xen.gz nosmp noacpi --- vmlinuz ramdisk=30720 ramdisk_blocksize=1024 root=/dev/ram0 --- initrd.img
>
> Here is a link to the page where I found this bug report for the
> EXT2-fs ramdisk_blocksize:
>
> http://wiki.systemimager.org/index.php/Troubleshooting#Ramdisk_too_small.3F_Getting_errors.3F
>
> I can provide or post these updates on the wiki if you would prefer.

All help keeping the Syslinux wiki in shape is appriceated.


> Thank you for all your help.
> Eric Nicholson


Cheers
Geert Stappers

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.