CentOS virt - Nov 2009 - Fedora 12 2.6.31.5-127.fc12 domU on CentOS 5.4 2.6.18-164.6.1.el5xen fails to boot

Doing a kickstart install of Fedora 12 results in a non-bootable image.
>From a virt-maanger instance, the error produced when trying to run the domU
is:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 498, in
run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 573, in
startup
    self.vm.create()
  File "/usr/lib64/python2.4/site-packages/libvirt.py", line 287, in
create
    if ret == -1: raise libvirtError ('virDomainCreate() failed',
dom=self)
libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err
"Error creating domain: Boot loader didn't return any data!")

If you drop to the command line to see what pygrub gets back, you get:

# pygrub /var/lib/xen/images/fedora12.img
Traceback (most recent call last):
  File "/usr/bin/pygrub", line 677, in ?
    fs = fsimage.open(file, get_fs_offset(file))
IOError: [Errno 95] Operation not supported

The kickstart worked perfectly in Fedora 11 on a CentOS 5.4 dom0.

I've tried investigating all sorts of grub options and even tried copying
kernel and initramfs files out from the domU to dom0 and booting from those with
no luck.  The only thing that does work is if I install Fedora 11 and then
perform an upgrade to Fedora 12.  I really don't want to have to deploy
machines this way.

Is anyone else experiencing this issue?  I can provide any further information
requested.  Basically, to repeat my error, install CentOS 5.4 with
Virtualization, then try to install a Fedora 12 domU.  The installation finishes
without error but you can't boot.  The systems are all x86_64.

Thanks.

Charles

Interesting...  I tried something similar using KOAN/Cobbler and believe 
that is the error I saw as well...

On Mon, 23 Nov 2009, Charles J Gruener wrote:
> Doing a kickstart install of Fedora 12 results in a non-bootable image.
>
>> From a virt-maanger instance, the error produced when trying to run the
domU is:
>
> Traceback (most recent call last):
>  File "/usr/share/virt-manager/virtManager/engine.py", line 498,
in run_domain
>    vm.startup()
>  File "/usr/share/virt-manager/virtManager/domain.py", line 573,
in startup
>    self.vm.create()
>  File "/usr/lib64/python2.4/site-packages/libvirt.py", line 287,
in create
>    if ret == -1: raise libvirtError ('virDomainCreate() failed',
dom=self)
> libvirtError: POST operation failed: xend_post: error from xen daemon:
(xend.err "Error creating domain: Boot loader didn't return any
data!")
>
> If you drop to the command line to see what pygrub gets back, you get:
>
> # pygrub /var/lib/xen/images/fedora12.img
> Traceback (most recent call last):
>  File "/usr/bin/pygrub", line 677, in ?
>    fs = fsimage.open(file, get_fs_offset(file))
> IOError: [Errno 95] Operation not supported
>
> The kickstart worked perfectly in Fedora 11 on a CentOS 5.4 dom0.
>
> I've tried investigating all sorts of grub options and even tried
copying kernel and initramfs files out from the domU to dom0 and booting from
those with no luck.  The only thing that does work is if I install Fedora 11 and
then perform an upgrade to Fedora 12.  I really don't want to have to deploy
machines this way.
>
> Is anyone else experiencing this issue?  I can provide any further
information requested.  Basically, to repeat my error, install CentOS 5.4 with
Virtualization, then try to install a Fedora 12 domU.  The installation finishes
without error but you can't boot.  The systems are all x86_64.
>
> Thanks.
>
> Charles
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
Scot P. Floess
27 Lake Royale
Louisburg, NC  27549

252-478-8087 (Home)
919-890-8117 (Work)

Chief Architect JPlate   http://sourceforge.net/projects/jplate
Chief Architect JavaPIM  http://sourceforge.net/projects/javapim

Architect Keros          http://sourceforge.net/projects/keros

This looks like your host doesn't support the filesystem your domU's
using.  I think Fedora's on ext4 by default.  One solution is to use
ext2/ext3 for the domU's boot media or partition.


Andri


On Mon, 2009-11-23 at 15:41 -0500, Charles J Gruener
wrote:
> Doing a kickstart install of Fedora 12 results in a non-bootable image.
> 
> >From a virt-maanger instance, the error produced when trying to run the
domU is:
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/engine.py", line 498,
in run_domain
>     vm.startup()
>   File "/usr/share/virt-manager/virtManager/domain.py", line 573,
in startup
>     self.vm.create()
>   File "/usr/lib64/python2.4/site-packages/libvirt.py", line 287,
in create
>     if ret == -1: raise libvirtError ('virDomainCreate() failed',
dom=self)
> libvirtError: POST operation failed: xend_post: error from xen daemon:
(xend.err "Error creating domain: Boot loader didn't return any
data!")
> 
> If you drop to the command line to see what pygrub gets back, you get:
> 
> # pygrub /var/lib/xen/images/fedora12.img
> Traceback (most recent call last):
>   File "/usr/bin/pygrub", line 677, in ?
>     fs = fsimage.open(file, get_fs_offset(file))
> IOError: [Errno 95] Operation not supported
> 
> The kickstart worked perfectly in Fedora 11 on a CentOS 5.4 dom0.
> 
> I've tried investigating all sorts of grub options and even tried
copying kernel and initramfs files out from the domU to dom0 and booting from
those with no luck.  The only thing that does work is if I install Fedora 11 and
then perform an upgrade to Fedora 12.  I really don't want to have to deploy
machines this way.
> 
> Is anyone else experiencing this issue?  I can provide any further
information requested.  Basically, to repeat my error, install CentOS 5.4 with
Virtualization, then try to install a Fedora 12 domU.  The installation finishes
without error but you can't boot.  The systems are all x86_64.
> 
> Thanks.
> 
> Charles
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt

>> On Tue, 2009-11-24 at 14:11 -0500, Charles J Gruener wrote:
>>> Well, I found the issue.  Anyone care to help me figure out how to
get this resolved?
>>> 
>>> https://bugzilla.redhat.com/show_bug.cgi?id=529846
>>> 
>>> Charles
To follow up on this post, the bugzilla entry above has been updated to include
an updates.img file that works perfectly.  I can now format an ext3 partition
for /boot and kickstart my Fedora 12 domU installs on a CentOS 5.4 dom0.

I hope this helps others who may experience this issue in the future.

Charles

----- "Scot P. Floess" <sfloess at nc.rr.com> wrote:
> It sure does...I am running it now...
This has affected F8, F10, 5.3, and so on for a few years. I wouldn't count
on it ever working unless you dig up the patches and figure out how to apply
them yourself, or find someone who has. :) If you want, you can dig up all of
the issues in Red Hat's bugzilla. Here's a recent one that may help you
out: https://bugzilla.redhat.com/show_bug.cgi?id=528053

-- 
Christopher G. Stach II