I've installed xen on top of FC5 as the dom0 and am running into trouble starting my first domU. I'm following the FedoraXenQuickstartFC5 here: http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 Here's the dom0: [root@db4 ~]# uname -a Linux db4.rnmd.net 2.6.16-1.2122_FC5xen0 #1 SMP Sun May 21 15:34:43 EDT 2006 i686 i686 i386 GNU/Linux And the command to install: [root@db4 ~]# xenguest-install.py -n xendomain1 -f /home/xen/xendomain1 -s 25 -r 256 -l http://ops1.rnmd.net/fedora/core/5/i386/os -x ks=http://ops1.rnmd.net/kickstart/cfgs/ks-fedora-core-5-xen-guest.cfg And the result: sending termination signals...done sending kill signals...done disabling swap... /dev/mapper/VolGroup00-LogVol01 unmounting filesystems... /mnt/runtime done disabling /dev/loop0 /proc done /dev/pts done /sys done /tmp/ramfs done /selinux done /mnt/sysimage/boot done /mnt/sysimage/proc done /mnt/sysimage/sys done /mnt/sysimage/selinux done /mnt/sysimage/dev done /mnt/sysimage done rebooting system Restarting system. If your install completed successfully, you can restart your guest by running 'xm create -c xendomain1'. [root@db4 ~]# xm create -c xendomain1 Using config file "/etc/xen/xendomain1". Going to boot Fedora Core (2.6.15-1.2054_FC5smp) kernel: /vmlinuz-2.6.15-1.2054_FC5smp initrd: /initrd-2.6.15-1.2054_FC5smp.img Error: (9, 'Bad file descriptor') It looks to me like the problem is that xm create is trying to boot a non xen Kernel. Anyone else seeing this behavior? Thanks. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192911
