Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3

[Bráulio Gergull <gergull@xxxxxxxxxxxxx>]

Hi Lars,

On Feb 09, 2006 01:08 PM, Lars Braeuer <lbraeuer@xxxxxxxx> wrote:

> Hi Braulio,
> 
> thanks for the tip. After the update the system hangs with a kernel
> panic, right after the (XEN)
> stuff on top.
> Can't exactly tell what it is, because the output of the kernel panic
> fills the screen
> an the panic itself locks up the keyboard.

Hmmm, in SuSE 9.3 there was a bug in mkinitrd that would insert a splash
screen in initrd that would cause dom0 to crash when loading initrd. I
thought it was corrected in SuSE 10.0, at least I don't remember if I
had to tune initrd myself in SuSE 10.0.

Anyway, you can try the following:

- Boot with the default kernel (not XEN);

- Build a custom initrd without the splash screen:

mkinitrd -k vmlinuz-2.6.13-15.7-xen -i initrd-xen.custom -s 0

This will a initrd without the splash screen (it wouldn't be used with
the xen kernel anyway).

If you want to tweak the list of modules that will be included you can
edit the parameter INITRD_MODULES in /etc/sysconfig/kernel before
running mkinitrd.

Then edit /boot/grub/menu.lst and change the initrd line accordingly.

BTW, you may also want to run SuSEconfig, since it does some
verifications and cleanup.

Reboot into the xen kernel.

I hope that it works.

rgrds,
Braulio Gergull


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