RE: [Xen-users] Howto debug initrd image?

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

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Reiner Dassing
> Sent: 03 May 2007 09:47
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Howto debug initrd image?
> 
> Hello,
> 
> I don't know whether I am in the right list, but I will try!
> 
> My main question is:
> Is it possible to debug initrd scripts during the boot process?
> Or, what the hell is wrong with my setup?
> 
> I set up PE1850 with Debian/etch and installed the necessary drivers
> into the kernel. It boots, I should be happy.
> 
> Then I installed Xen3.0.4 which wants to make use of an 
> initrd image to
> be as flexible as possible. The drivers are not in the kernel, they
> should be loaded as modules.
> After trying now for a lot of time, the boot process ends up with
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(0,0)

I was hoping that someone else would come up with an answer, but it
seems that isn't the case... So my basic answer is:

A (good?) way to debug initrd problems is to compare the output during
boot between a working and a non-working setup (e.g. native Linux and
Xenified Linux in this case). That will usually indicate some driver not
being loaded in the failing case (either because the driver doesn't
exist, or it's bailing out on some error-condition). 

You may find using a serial port to log the boot-messages is helpful
here. 

--
Mats



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