Hi Rusty,
On 22.05.2007, at 01:45, Rusty Russell wrote:
On Mon, 2007-05-21 at 10:13 +0200, Jan Michael wrote:
Salut Rusty,
On 21.05.2007, at 08:16, Rusty Russell wrote:
Hmm, perhaps your kernel doesn't have INITRD support? The
default Xen
kernel works (at least, for me on i386 it does)...
Hm. No. Unfortunately the kernel I'm using has INITRD support,
Hi Jan!
Hmm, it has found the initrd, and ramdisk seems to be there. Any
chance you can send your kernel config? Obviously we want it to "just
work" with whatever configs it can...
Sure. No problem. Please find attached our kernel config for domUs.
Did you see the mail from Jeremy?
On 21.05.2007, at 15:13, Jeremy Fitzhardinge wrote:
66 XENBUS: Device with no driver: device/vbd/51713
67 XENBUS: Device with no driver: device/vif/0
looks worrysome. Do you have netfront and blkfront compiled into
(your
kernel, either built-in or as modules in your initrd)?
Though it seems you have a more basic problem with mounting the
initrd.
I can say that we are using a kernel builf from the attached kernel
config and a special initrd image for our domUs.
The initrd image contains the modules xenblk.ko and xennet.ko. So
netfront and blkfront are not compiled into the kernel.
Our linux gurus made the kernel and the initrd image. I think I have
to integrate those modules into the initrd image you are using and
have to load them. But at this point I have no knowledge how to do
this...
Cheers,
Jan
config-2.6.9-42.0.3.EL.cernxenU
Description: Binary data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home