WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] probs running stuff from initrd

On Mon, 3 Apr 2006, Petersson, Mats wrote:

-----Original Message-----

Hello all

Now I may be way of whack here, so please forgive me.

I'm trying to merge xen with redhat's config-netboot. The
idea being a kinda stateless domU. For those that haven't
seen you share a rootfs and then bind mount all the
individual files over then top, and the redhat gui builds all
the pxeboot config and stuff for you if you want a diskless
client. I thought this would be nice for our domU's but
obviously don't need the pxe bit.

I've got nfsroot domU's working, and was just wondering if it
would be possible to mount the diskless initrd and run the
diskless script from inside that.

First of all what do you think root should equal. For nfsroot
you set it to /dev/nfs but the pxeconfig that get produced
uses /dev/ram0

I've also set this

ramdisk = "/tftpboot/linux-install/RHEL4.1/initrd.img"

and then tried to pass init=disklessrc

But it does this ( with root= /dev/ram0 ):-

RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 5000KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 184k freed
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init=
option to kernel.

Now that initrd has got a console (and a null) and I've tried
passing various init= lines but nothing works. I've also
tried rebuilding the initrd with links to init and linuxrc,
but nothing.

What would I need to pass as a root= to be able to get it to
run something in the initrd?

The problem isn't with trying to run something in initrd [at least not
directly], but most likely failing when the system tries to mount your
"root" directory (/).

It's either missing the /dev/<something> that you've said is "/", or
it's missing some driver needed to access this.

I've seen this a fair number of times (both on my own system, due to
missing /dev/something or due to missing driver) and people on this list
suffering the same thing.

You may need to compile more stuff into your XenU kernel to make it work
right...


I can't think what else I'd need. All the rootnfs stuff is ok. I've checked all the initrd and ramdisk stuff and its all in. I've also copied in the /dev from the working root image into the initrd, but still no joy.

Cheers
Lee



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

<Prev in Thread] Current Thread [Next in Thread>