Re: [Xen-devel] What is the implication to use 'module'directive instead of 'initrd' to load ramdis

["Liang Yang" <multisyncfe991@xxxxxxxxxxx>]

Jan,

I used SINGLE module to load kernel and SINGLE intird to load ramdisk in 
grub.conf file.
title Xen Unstable /Red Hat Enterprise Linux 2.6.16.33
kernel /xen.gz console=vga
module /vmlinuz-2.6-xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet 
console=tty0
initrd /initrd-2.6.16.33-xen.img

Based on what you explained, this should be fine. However, Xen Linux still 
got a panic message: Linux kernel must be loaded before ramdisk.
How do you explain this?

Thanks,

Liang

----- Original Message ----- 
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
To: "Liang Yang" <multisyncfe991@xxxxxxxxxxx>
Cc: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>; 
<xen-users@xxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, January 10, 2007 3:09 AM
Subject: Re: [Xen-devel] What is the implication to use 'module'directive 
instead of 'initrd' to load ramdis

> >I noticed Xen used Module directive to load RAMDISK for XenLinux in boot
> > grub config file instead of regular initrd. Why can't we use initrd here? 
> > I
> > tried to change back to initrd and Linux reports an error kernal panic
> > message: Linux kernel must be loaded before ramdisk.
> >
> > Could anyone here explain about this?
> 'initrd' is equivalent to 'module' except that there can only be a single 
> initrd
> statement per boot option. Obviously you need two modules (the kernel
> and its initrd), hence you can't use 'initrd' here.
>
> Jan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel