Hmm...the FC5 install document did not include instructions to install xenU. The FC4 one did. Anyway I installed the xenU package and it worked. Further problems though: The guest installs I did *before* installing still refuse to start. The ones I did after start fine. I deleted the disk image for the old ones and deleted the config files in /etc/xen. Still I get the same error message when I create a new VM with that name. Where does Xen store info about the previously installed VMs ? Thanks, -ashe On 5/14/06, Riaan van Niekerk <riaan@xxxxxxxxxxxxxx> wrote:
Mark A Heilpern wrote: > Looks like you don't have the xenU rpm installed. I think the pygrub bootloader needs it. Try installing (into dom0) kernel-xenU-2.6.16-1.2080_FC5. > You do not need the xenU RPM installed into dom0 the python script grab kernel and ramdisk from the installation location. Are you sure your install tree is set up correctly? Copy everything from CD1/DVD to /mnt, since the installer takes its kernel+initrd from ./images/xen, Riaan > > ------------------------- > Original Message: > From: Ashe Canvar <acanvar@xxxxxxxxx> > To: fedora-xen@xxxxxxxxxx > Date: Sunday, May 14 2006 03:27 PM > Subject: [Fedora-xen] xenguest-install.py issues > Hi all, > > I am following the FC5 Xen install page. However my xenU installs do > not seem to work using the python script. What am I doing wrong ? > > [root@medusa1 ~]# NM=m1b; export NM; /usr/sbin/xenguest-install.py -n > $NM -f /vmd/$NM/$NM.disk -s 5.1 -r 256 -l nfs:10.1.55.40:/mnt > > > Starting install... > Using config file "/etc/xen/m1b". > Error: Error creating domain: Kernel image does not exist: > /var/lib/xen/vmlinuz.oZFOHc > If your install has exited, you can restart your guest by running > 'xm create -c m1b'. Otherwise, you can reconnect to the console > by running 'xm console m1b' > [root@medusa1 ~]# xm create -c m1b > Using config file "/etc/xen/m1b". > Traceback (most recent call last): > File "/usr/bin/pygrub", line 256, in ? > cf = get_config(file, isconfig) > File "/usr/bin/pygrub", line 139, in get_config > raise RuntimeError, "Unable to read filesystem" > RuntimeError: Unable to read filesystem > Error: Boot loader didn't return any data! > [root@medusa1 ~]# > > > [root@medusa1 ~]# uname -a > Linux medusa1 2.6.16-1.2080_FC5xen0 #1 SMP Tue Mar 28 04:13:51 EST > 2006 i686 i686 i386 GNU/Linux > [root@medusa1 ~]# rpm -qa | grep -i xen > xen-3.0.1-4 > kernel-xen0-2.6.16-1.2080_FC5 > > > > Thanks ! > -ansh > > -- > > Fedora-xen@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- > > Fedora-xen@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
