[xen-tools] Re: No initrd?

[Asheesh Laroia]

On Fri, 23 Jun 2006, Steve Kemp wrote:

> On Fri, Jun 23, 2006 at 01:47:27AM -0400, Asheesh Laroia wrote:
>> With the Fedora Xen kernels we seem to have, Debian Sarge guests (I'm
>> being specific because I've tried no others) panic if you boot them with
>> the initrd.  Without the initrd, it boots fine.
>
>  That is very strange.

I tried setting the initrd to the Fedora 
/boot/initrd-2.6.16-1.2096_FC5xenU.img file, and it does work.  Sorry;  I 
must have specified the wrong initrd before.

>> Would you consider supporting an --initrd=none that would simply not
>> leave an initrd= line in the generated .cfg?
>
>  There should be no need, just set:
>
> initrd=
>
>  In /etc/xen-tools/xen-tools.conf

I've now commented out the initrd= line in /etc/xen/xen-tools.conf and set 
--initrd= on the command line.  I'm running with --verbose, and 
xen-create-image reports:

Kernel path    :  /boot/vmlinuz-2.6.16-1.2096_FC5xenU
initrd path    :  /boot/initrd.img-2.6.16-1-xen-686

I think that's a default built in to the program.  That's wrong.

I've now set "initrd=" in xen-tools.conf.  I'm also passing --initrd= on 
the command line.  Now it reports:

Kernel path    :  /boot/vmlinuz-2.6.16-1.2096_FC5xenU
initrd path    :

That worked just great.  It also worked without passing "--initrd=" on the 
command line.  It seems to set "ramdisk=''" in /etc/xen/whatever.cfg 
rather than simply omitting the line, but Xen deals with that okay 
apparently.

-- Asheesh.

-- 
Buckle up!