Re: init receiving SIGILL on XEN3_DOM0/amd64

[James Laird <abrasive%axdf.net@localhost>]

On Sun, May 18, 2008 at 03:24:43PM +0100, Matthias Scheler wrote:
> For some weird reason the problem went away after I fixed the line
> in "/grub/menu.lst":
> 
> title Xen 3.1 / NetBSD (hda0, serial)
>   root(hd0,0)
>   kernel (hd0,a)/xen.gz dom0_mem=718592 com1=115200,8n1
>   module (hd0,a)/netbsd rootdev=/dev/wd0a ro console=ttyS0 
>                         ^^^^^^^
> 
> According to the example this should read "bootdev" which results
> in the kernel asking for the root filesystem. With the above entry
> the machine boots.
> 
> Would anybody object if I correct that part of the HOWTO?

You know, I think bootdev is actually right.

When I supply rootdev= or nothing, I get it trying wd0 and asking.
My entry had bootdev=/dev/wd2a (the root).
I just changed it to bootdev=wd2 and it boots now (though python is dying 
horribly, that's another matter.)

So, yes, correct the howto by changing it to read bootdev=hd0 :)

This would suggest that the root/dump/fs/init prompting system is doing some 
damage somewhere, then.

Cheers
James