FW: [SSI-users] Xen and OpenSSI

[Owen C. <ow...@em...>]

Nearly there!!!

The problems seem to be caused by mismatched modules and kernel version.

I've now managed to build a working initrd, but the domU still refuses
to boot.

The problem is that the domU was originally booted using the kernel from
option-c, which is 2.6.11, and the initrd created from there.

The openssi kernel which it tells me to download is 2.6.10 and so the
domU can't find the relevant modules when it reboots with the openssi
kernel.

Is there an easy way to get around this (that doesn't involve building a
custom domU kernel!!)?

Owen

-----Original Message-----
From: Owen Campbell=20
Sent: 16 February 2006 11:53
To: 'ssi...@li...'
Subject: FW: [SSI-users] Xen and OpenSSI

Ok, I tried from scratch again and here's where I got to.....

When I run 'mkinitrd -o /tmp/initrd', I get

cpio: initrd/lib/libc.so.6 not created: newer or same age version exists
cpio: initrd/lib/libcluster.so.0 not created: newer or same age version
exists
4584+0 records in
4584+0 records out
4694016 bytes transferred in 0.291641 seconds (16095183 bytes/sec)
All of your loopback devices are in use!

And initrd is created in the /tmp directory

If I run 'modprobe loop' I get

modprobe: Can't open dependencies file
/lib/modules/2.6.11-ocxenu/modules.dep (No such file or directory)

So it looks like you were correct!!!

I'm afraid I've always avoided kernel building, so this is all a bit new
to me. Any ideas how I get the initrd created?

Owen

-----Original Message-----
From: Waeyenbergh, Sven [mailto:Sve...@at...]=20
Sent: 14 February 2006 16:22
To: ssi...@li...
Cc: Owen Campbell
Subject: RE: [SSI-users] Xen and OpenSSI

Owen,

"Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(1,0)" i think means that=20
your kernel cannot find or mount a (temporary) root filesystem on a
device with major 1 and minor 0.
There is only 1 device like that, and it's the ramdisk.

So your kernel cannot mount the filesystem in your initrd.
Did you create the initrd (and ftp to the domU) as intructed ?
Did the creation of this initrd (with the mkinitrd command) give you any
errors ?

An error that i saw again and again is that at the moment the initrd is
created, no loop drivers are loaded.
The mkinitrd command does not seem to load this module automatically,
so, on your dom0, do a "modprobe loop" and recreate the initrd and ftp
it again.

If that doesn't work, maybe you could mount the initrd on dom0 and have
a look inside ?

Greetings,
Sven

-----Original Message-----
From: Owen Campbell [mailto:ow...@em...]
Sent: 14 February 2006 12:32
To: ssi...@li...
Subject: [SSI-users] Xen and OpenSSI


Hi All,
I'm trying to get OpenSSI working on Xen and have hit a problem.
I'm following the instructions at
http://openssi.org/cgi-bin/view?page=3Ddocs2/1.9/debian/xen-howto.txt =
and
also the document at http://www.option-c.com/xwiki/OpenSSI=20
I've got as far as booting the domU with the OpenSSI kernel and I get
"Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(1,0)"
My base Xen installation is 2.07 on Debian Sarge using the packages from
option-c and I used the pre-built OpenSSI kernel.
My config file for the domU is:
#kernel =3D "/boot/xen-linux-2.6.11-ocxenu"
kernel =3D "......./xenU-vmlinuz"
ramdisk =3D "........./initrd"
memory =3D 64
name =3D "<hostname>"
disk =3D ['file........img,hda1,w','file.........img,hda2,w']
root =3D "/dev/hda1 ro"
#
vif =3D ['mac=3DAA:00:00:18:94:FB']
and /etc/fstab on the domU is
# Begin /etc/fstab
# <file system> <mount point>   <type>  <options>

/dev/hda1       /       ext3    defaults,errors=3Dremount-ro,node=3D1
0
/dev/hda2       swap    swap    sw,node=3D1       0       0
proc    /proc   proc    defaults,node=3D* 0       0
# End /etc/fstab
Does anyone have any ideas as to where I've gone wrong?
************************************************************************
****
Disclaimer:=20
This electronic transmission and any files attached to it are strictly=20
confidential and intended solely for the addressee. If you are not=20
the intended addressee, you must not disclose, copy or take any
action in reliance of this transmission. If you have received this=20
transmission in error, please notify the sender by return and delete
the transmission.  Although the sender endeavors to maintain a
computer virus free network, the sender does not warrant that this
transmission is virus-free and will not be liable for any damages=20
resulting from any virus transmitted.=20
Thank You.
************************************************************************
****