RE: [Xen-users] Xen 3.0.4 on RH EL 4.4 - can't make it boot kerne l

["Petersson, Mats" <Mats.Petersson@xxxxxxx>]

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Foreman, Tim
> Sent: 01 March 2007 15:30
> To: 'Omer Khalid'
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Xen 3.0.4 on RH EL 4.4 - can't make 
> it boot kerne l
> 
> I didn't want to make the Xen kernel the default until I was
> sure that it would boot correctly.

Sensible. 
> 
> When I put the root=LABEL=/ on it I get an error:
> 
> mkrootdev: label / not found

Yes, I've had problems using "LABEL=" on my system too - and it's really
not any difference - it's just easier to change the root drive if you
use LABEL= on the kernel line. 

Can you post your /etc/fstab from the system you're trying to boot?

--
Mats
> 
> --Tim
> 
> -----Original Message-----
> From: okhalid.cern@xxxxxxxxx 
> [mailto:okhalid.cern@xxxxxxxxx]On Behalf Of
> Omer Khalid
> Sent: Thursday, March 01, 2007 9:24 AM
> To: Foreman, Tim
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Xen 3.0.4 on RH EL 4.4 - can't make 
> it boot kernel
> 
> 
> Hi Tim,
> 
> The first thing I noticed in your grub.conf is that your xen 
> configuration
> have index value 0f 2, while the default=0. It should be 
> default=2. I hope
> this should sort the obvious problem.
> 
> Secondly, why are you not using root=LABEL=/ rather root=/dev/hda1! 
> 
> Cheers
> Omer
> 
> 
> On 3/1/07, Foreman, Tim <tforeman@xxxxxxxxx> wrote:
> I'm trying to build a Xen server on Enterprise 4.4 and I can't
> get the Xen kernel to boot.
> 
> I installed the kernel rpm and the Xen rpm and my grub.conf looks
> like this:
> 
> # grub.conf generated by anaconda 
> #
> # Note that you do not have to rerun grub after making 
> changes to this file
> # NOTICE:  You do not have a /boot partition.  This means that
> #          all kernel and initrd paths are relative to /, eg.
> #          root (hd0,0) 
> #          kernel /boot/vmlinuz-version ro root=/dev/hda1
> #          initrd /boot/initrd-version.img
> #boot=/dev/hda
> default=0
> timeout=5
> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> hiddenmenu
> title Red Hat Enterprise Linux ES ( 2.6.9-42.ELsmp)
>         root (hd0,0)
>         kernel /boot/vmlinuz-2.6.9-42.ELsmp ro root=LABEL=/
>         initrd /boot/initrd-2.6.9-42.ELsmp.img
> title Red Hat Enterprise Linux ES-up (2.6.9-42.EL)
>         root (hd0,0) 
>         kernel /boot/vmlinuz-2.6.9-42.EL ro root=LABEL=/
>         initrd /boot/initrd-2.6.9-42.EL.img
> title Red Hat Enterprise Linux ES Xen (2.6.16.33-xen_3.0.4.1)
>         root (hd0,0)
>         kernel /boot/xen- 3.0.4.1.gz
>         module /boot/vmlinuz-2.6.16.33-xen_3.0.4.1 ro root=/dev/hda1
>         module /boot/initrd-2.6.16.33-xen_3.0.4.1.img
> 
> When I try and boot the Xen kernel it stops with the following errors:
> 
> Loading ide-disk.ko module
> ide_disk: no version for "struct_module" found: kernel tainted.
> Creating root device
> Mounting root filesystem
> mount: error 6 mounting ext2
> mount: error 2 mounting none 
> Switching to new root
> switchroot: mount failed: 22
> umount /initrd/dev failed: 2
> Kernel panic - not syncing: Attempted to kill init!
> 
> I did some googling and found some indications that it might 
> have been 
> related to using the ext3 filesystem, so I rebuild the server 
> with ext2
> and got the same results.
> 
> Any suggestions?
> --
> Timothy W. Foreman ~ Security Administrator ~ tforeman@xxxxxxxxx 
> (651) 365-4181     ~ Internet Broadcasting  ~ www.ibsys.com
> --
> The Onion: Have you decided what you want to be when you grow up?
> Berkeley Breathed: Dad. The rest is frosting. 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 
> 



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