Hello all,
I'm installing xen3.1 on an Ubuntu Feisty Fawn 7.04 using the tarball
source. Dom0 works good now! and I can also start domUs, the problem
is that I get this error when I do an xm create -c sistema.sxp
Couldnt get a file descriptor referring to the console
modprobe: FATAL: Could not load /lib/modules/2.6.18-xen/modules.dep: No such file or directory
modprobe: FATAL: Could not load /lib/modules/2.6.18-xen/modules.dep: No such file or directory
It shows this error about 8 times, but eventually the domU starts and
apparently everything works fine. The point is that I'm trying to find
out why it happens, because I need this machine to be stable.
I have tried many things to solve this and nothing seems to work. I
compiled my own kernel. Also I decompressed the ram disk to look for
the file that is missing, it's not there so I put it there manually and
made a cpio and gzip, but when I use the new-initrd.img on the domU it
goes the same and if I try to use my own generated initrd with dom0
doen't boot up and stalls in the root file system checkup.
This is my sistema.sxp file:
kernel = "/boot/xen/vmlinuz-2.6.18-xen"
ramdisk = "/boot/xen/new-initrd.img"
memory = 128
name = "SistemaPrueba"
vif = ['mac=4E:4F:53:59:53:00' ]
disk= [ 'phy:/dev/vm/sistema,sda1,w', 'phy:/dev/vm/sistema-swap,sda2,w' ]
hostname="SistemaPrueba"
root = "/dev/sda1 ro"
extra = "4"
Yes, I'm using the same xenKernel for the dom0 and the domU. The domU
is a Feisty debootstrap system with openssh-server that responds. And
it's mounted on a logical volume (which might be the source of the
problem)
Thanks a lot,
Miguel Araujo
