Xen users - Aug 2006 - Problems building a guest os on Fedora Core 5

I''m having trouble getting any guest OSes to run on my Fedora Core  
build unless I use the xenguest-install.py script that comes with the  
Fedora distro.  I''ve tried building my own and grabbing images from  
http://jailtime.org/ but I get the same error every time.

Error: Kernel image does not exist: /boot/vmlinuz-2.6.15-1.2054_FC5xenU

But the kernel image is in the guest os image:

[root@dhcp-158-32-168-192 ~]# mount -o loop /vmroot/system1/fc5 /mnt
[root@dhcp-158-32-168-192 ~]# ls /mnt/boot/
config-2.6.15-1.2054_FC5xenU  initrd-2.6.15-1.2054_FC5xenU.img   
System.map-2.6.15-1.2054_FC5xenU
grub                          lost+found                         
vmlinuz-2.6.15-1.2054_FC5xenU

I''ve tried numerous configuration file changes, but this is what I  
have currently

name = "spawn02"
memory = 256
disk = [ ''file:/vmroot/system1/fc5,xvda,w'' ]
vif = [ ''mac=00:16:3e:1d:63:cf'' ]
uuid = "1da7f026-6bcb-0aa5-c383-d30eedec932f"
#bootloader="/usr/bin/pygrub"
kernel = "/boot/vmlinuz-2.6.15-1.2054_FC5xenU"
ramdisk = "/boot/initrd-2.6.15-1.2054_FC5xenU.img"

on_reboot   = ''restart''
on_crash    = ''restart''

I''ve tried this with and withouth the ramdisk and using the pygrub  
boot loader instead of specifying the kernel in the config but it  
continues to fail for me.  I don''t know if this is related but I  
noticed that the images created by the xenguest-install.py script  
cannot be mounted the way the ones built from the xen user guide  
can.  The ''file'' command shows them as different types too:

[root@dhcp-158-32-168-192 ~]# file /vmroot/system1/fc5*
/vmroot/system1/fc5:   Linux rev 1.0 ext3 filesystem data (large files)
/vmroot/system1/fc5.1: x86 boot sector, code offset 0x48

The fc5.1 is the image built by the xenguest-install.py script.

Can anyone point me in the right direction here?

Thanks in advance
Peter C.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Wed, Aug 02, 2006 at 12:45:48PM -0700, Peter Cornelius wrote:
> Error: Kernel image does not exist: /boot/vmlinuz-2.6.15-1.2054_FC5xenU
> 
> But the kernel image is in the guest os image:
  This is your problem.

  The kernel specified in the Xen configuration file is a kernel
 on the *host*

  You don''t need a kernel at all in the guest system ...
> Can anyone point me in the right direction here?
  Point to the kernel on the host which is presumably correctly
 specified in the instances you can boot using the python script
 you mention.

Steve
-- 
Debian GNU/Linux System Administration
http://www.debian-administration.org/


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Thank you Steve, that got it going.  Weird thing, there are no other  
domU kernels in my host systems boot even tho I''ve built, and am  
running, 2 guest systems with the fedora scripts.  I guess they''re  
doing something unusual.

Anyway, thanks again.

PC

On Aug 2, 2006, at 12:55 PM, Steve Kemp wrote:
> On Wed, Aug 02, 2006 at 12:45:48PM -0700, Peter Cornelius wrote:
>
>> Error: Kernel image does not exist: /boot/ 
>> vmlinuz-2.6.15-1.2054_FC5xenU
>>
>> But the kernel image is in the guest os image:
>
>   This is your problem.
>
>   The kernel specified in the Xen configuration file is a kernel
>  on the *host*
>
>   You don''t need a kernel at all in the guest system ...
>
>> Can anyone point me in the right direction here?
>
>   Point to the kernel on the host which is presumably correctly
>  specified in the instances you can boot using the python script
>  you mention.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users