Re: [gentoo-user] New kernel does not boot up on remote host

[Galevsky <galevsky@gmail.com>]

2007/7/6, Albert Hopkins <marduk@gentoo.org>:
> On Fri, 2007-07-06 at 00:44 +0200, Galevsky wrote:
> > and my grub.conf:
> >
> > ### START (grub.conf)
> > sd-4421 boot # cat /boot/grub/grub.conf
> > # Customized boot procedure
> >
> > default 0
> > timeout 1
> > #fallback 1 2
> >
> > title Gentoo Linux 2.6.16-gentoo_xen_dom0
> >   root (hd0,0)
> >   kernel /boot/vmlinuz-2.6-xen ro root=/dev/sda2
> >
> >
> > title Gentoo Linux 2.6.20-r8
> >   root (hd0,0)
> >   kernel /boot/vmlinuz-2.6.20-gentoo-r8 ro root=/dev/sda2
> >
> >
> > title Gentoo Linux 2.6.18-r4-dedibox_r6_final
> >   root (hd0,0)
> >   kernel /boot/ref/2.6.18-gentoo-r4dedibox_r6_final ro root=/dev/sda2
> > ### END (grub.conf)
>
> Wow, it really does make a difference when we can see the configuration!
>
> Actually you are not using savedefault like I was assuming.  Which
> basically means fallback only works when grub fails to load the kernel.

ya, and that is the behavior I want. I know about the savedefault
feature but  I doesn't need it in my case.

> You said you followed the "HOWTO Xen and Gentoo" but looks like you
> ignored section 6 on configuring the boot loader.  It should look more
> like this:
>
>         title Gentoo Linux 2.6.16-gentoo_xen_dom0
>             root (hd0,0)
>             kernel /boot/xen.gz dom0_mem=98M
>             module /boot/vmlinuz-2.6.20-gentoo-r8 ro root=/dev/sda2
>
> Likely the dom0 kernel is failing because it expects to be run within
> the hypervisor.  You need to load that first as in the above.
>
> Hope this helps.
>

True !!!

Due to lots of changes I made from the start, I forgot in the end the
hypervisor itself !!!

Of course it will help ;o)

> --
> Albert W. Hopkins

Big *THANKS* to you, and to Dan Farrell too, and sorry for such a
mistake... shame on me.

Gal'
-- 
gentoo-user@gentoo.org mailing list