Fedora 10 on RHEL5.3 x86_64

[Mike McGrath]

Anyone having issues doing F10 on RHEL5.3?  I'm seeing this (with debug
enabled:

hu, 12 Feb 2009 16:00:18 DEBUG    No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:18 DEBUG    No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:18 DEBUG    No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:18 DEBUG    No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:19 DEBUG    No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:19 DEBUG    No guest running yet
virDomainLookupByName() failed Domain not found:
xenUnifiedDomainLookupByName
Thu, 12 Feb 2009 16:00:19 DEBUG    Removing
/var/lib/xen/virtinst-vmlinuz.V9IWB3
Thu, 12 Feb 2009 16:00:19 DEBUG    Removing
/var/lib/xen/virtinst-initrd.img.tUWkKJ
ERROR:  It appears that your installation has crashed.  You should be able
to find more information in the logs


Except the info in the logs isn't very revealing.  I get this when doing a
virt-install -p.

any ideas?

	-Mike

[Olivier Renault]

Mike McGrath wrote:
>  Anyone having issues doing F10 on RHEL5.3?  I'm seeing this (with
> debug
>  enabled:
>  
>  hu, 12 Feb 2009 16:00:18 DEBUG    No guest running yet
>  virDomainLookupByName() failed Domain not found:
>  xenUnifiedDomainLookupByName
>  Thu, 12 Feb 2009 16:00:18 DEBUG    No guest running yet
>  virDomainLookupByName() failed Domain not found:
>  xenUnifiedDomainLookupByName
>  Thu, 12 Feb 2009 16:00:18 DEBUG    No guest running yet
>  virDomainLookupByName() failed Domain not found:
>  xenUnifiedDomainLookupByName
>  Thu, 12 Feb 2009 16:00:18 DEBUG    No guest running yet
>  virDomainLookupByName() failed Domain not found:
>  xenUnifiedDomainLookupByName
>  Thu, 12 Feb 2009 16:00:19 DEBUG    No guest running yet
>  virDomainLookupByName() failed Domain not found:
>  xenUnifiedDomainLookupByName
>  Thu, 12 Feb 2009 16:00:19 DEBUG    No guest running yet
>  virDomainLookupByName() failed Domain not found:
>  xenUnifiedDomainLookupByName
>  Thu, 12 Feb 2009 16:00:19 DEBUG    Removing
>  /var/lib/xen/virtinst-vmlinuz.V9IWB3
>  Thu, 12 Feb 2009 16:00:19 DEBUG    Removing
>  /var/lib/xen/virtinst-initrd.img.tUWkKJ
>  ERROR:  It appears that your installation has crashed.  You should be able
>  to find more information in the logs
>  
>  
>  Except the info in the logs isn't very revealing.  I get this when doing a
>  virt-install -p.
>  
>  any ideas?
>   
There is no xen kernel within F10 so you will need to install it as a FV 
   VM.

Olivier

[Mark McLoughlin]

On Thu, 2009-02-12 at 21:21 +0100, Olivier Renault wrote:

>  There is no xen kernel within F10 so you will need to install it as
> a
>  FV VM. 
Yes, there is - the bare-metal kernel has pv_ops Xen support. You may
have been bitten by this bug, though:

  https://bugzilla.redhat.com/470905
    anaconda installs the wrong kernel for i686 xen guests.

Cheers,
Mark.

[Mike McGrath]

On Fri, 13 Feb 2009, Mark McLoughlin wrote:

>  On Thu, 2009-02-12 at 21:21 +0100, Olivier Renault wrote:
>
>  > There is no xen kernel within F10 so you will need to install it as a
>  > FV VM.
>
>  Yes, there is - the bare-metal kernel has pv_ops Xen support. You may
>  have been bitten by this bug, though:
>
>    https://bugzilla.redhat.com/470905
>      anaconda installs the wrong kernel for i686 xen guests.
>  
Its not even getting to stage 2 during install I'm afraid.

	-Mike