Fedora xen - Jun 2006 - Xenguest-install.py Tries to boot non-xen kernel Bad File Descriptor

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

Hi,

On Thu, 2006-06-01 at 15:42 -0700, Demetri Mouratis wrote:
> [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
...
> [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.
Looks like it.  What are the contents of your kickstart file?  A non-
kickstart domU install definitely leaves the domU, not the smp, kernel
installed.

-_Stephen

On 6/6/06, Stephen C. Tweedie <sct@redhat.com>
wrote:
> Hi,
>
> On Thu, 2006-06-01 at 15:42 -0700, Demetri Mouratis wrote:
>
> > [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
>
> ...
>
> > [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.
>
> Looks like it.  What are the contents of your kickstart file?  A non-
> kickstart domU install definitely leaves the domU, not the smp, kernel
> installed.
>
> -_Stephen
Hi Stephen,

Thanks for the reply. Attached is my ks file.  I don''t think there is
anything funky going on there.  Basically, I did a manual install from
the xenguest-install script then poached the resultant anaconda-ks.cfg
file.  The strange thing from my perspective, and I''ve noted this in
the bug, is that invoking xenguest-install non-interactively, i.e.,
without the -x option, produces a working domU booting the correct
kernel.

Thanks.

# Kickstart file generated by Demetri

install
url --url http://ops1.rnmd.net/fedora/core/5/i386/os
lang en_US.UTF-8
langsupport --default=en_US.UTF-8 en_US.UTF-8
keyboard us
network --device eth0 --bootproto dhcp
rootpw --iscrypted _removed to protect the innocent_
firewall --disabled
selinux --disabled
authconfig --enableshadow --enablemd5
timezone America/Los_Angeles
bootloader --location=mbr
reboot
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
clearpart --all --drives=xvda --initlabel
part /boot --fstype ext3 --size=100 --ondisk=xvda
part pv.2 --size=0 --grow --ondisk=xvda
volgroup VolGroup00 --pesize=32768 pv.2
logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00
--size=272 --grow --maxsize=544

%packages
@ admin-tools
@ text-internet
@ dialup
@ smb-server
@ web-server
@ printing
@ server-cfg
kernel-smp
grub
lvm2
e2fsprogs

%post

Hello All,

Anybody have the doc concerning how to install the network with Xen ?

Each time to define the vif in my file for to load the DomU i have error

Vif [ '' '' ]


Many Thanks

Eric

Hi,

On Tue, 2006-06-06 at 09:40 -0700, Demetri Mouratis wrote:
> Thanks for the reply. Attached is my ks file.  
...
> %packages
> @ admin-tools
> @ text-internet
> @ dialup
> @ smb-server
> @ web-server
> @ printing
> @ server-cfg
> kernel-smp
Hmm, does it work if you replace this with kernel-xenU?
> Basically, I did a manual install from
> the xenguest-install script then poached the resultant anaconda-ks.cfg
> file.
Well, if that''s the result of a xenguest-install.py, it looks like an
anaconda bug in the kickstart generation --- I''ll try to reproduce
this.

Cheers,
 Stephen

On 6/7/06, Stephen C. Tweedie <sct@redhat.com> wrote:
>
> Well, if that''s the result of a xenguest-install.py, it looks like
an
> anaconda bug in the kickstart generation --- I''ll try to reproduce
this.
>
Stephen,

Don''t bother.

On closer examination I had put my anaconda-ks.cfg from my base FC5
install under ks-fedora-core-5-xen-guest.cfg in place of the one
resulting from invoking xenguest-install.py.  Thanks for finding my
mistake.  I''m verifying it now and will note in the bug accordingly.

Thanks!