Xen users - Jul 2007 - Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'')

Hello,

I''ve been using Xen 3.0.4 successfully on a debian dom0 with a p4 3.2
ghz
processor, but with a non VT chipset.

I''ve just recently purchase a Core 2 Duo, and thought about migrating
my
guests to be vmx guests. I followed the guide at
http://wiki.xensource.com/xenwiki/VmxQuickstartGuide, but having troubles
starting the guest.

If I do "xm create -f <whatever>.cfg -c", I see a pygrub menu,
but it
bombs out when trying to load the kernel.

I see the following in /var/log/xen/domain-builder-ng.log:

xc_dom_release: called
xc_dom_allocate: cmdline="root=/dev/hda1 ro quiet splash",
features=""
xc_dom_kernel_file: filename="/var/run/xend/boot/boot_kernel.25ua2U"
xc_dom_malloc_filemap    : 1723 kB
xc_dom_ramdisk_file: filename="/var/run/xend/boot/boot_ramdisk.2aUKzk"
xc_dom_malloc_filemap    : 6646 kB
xc_dom_boot_xen_init: ver 3.1, caps xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p
xc_dom_parse_image: called
xc_dom_find_loader: trying ELF-generic loader ... failed
xc_dom_find_loader: trying multiboot-binary loader ... failed
xc_dom_core.c:495: panic: xc_dom_find_loader: no loader found

Anyone have any suggestions at all? I essentially just created a new image
file, used fdisk to create the partition, and installed grub into the mbr,
then copied the contents of the OS from the old disk image using "cp
-a".

Regards,
MiLK_MaN


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

> I''ve just recently purchase a Core 2 Duo, and thought about
migrating my
> guests to be vmx guests. I followed the guide at
> http://wiki.xensource.com/xenwiki/VmxQuickstartGuide, but having troubles
> starting the guest.
>
> If I do "xm create -f <whatever>.cfg -c", I see a pygrub
menu, but it
> bombs out when trying to load the kernel.
>
> I see the following in /var/log/xen/domain-builder-ng.log:
>
> xc_dom_release: called
> xc_dom_allocate: cmdline="root=/dev/hda1 ro quiet splash",
features=""
> xc_dom_kernel_file:
filename="/var/run/xend/boot/boot_kernel.25ua2U"
> xc_dom_malloc_filemap    : 1723 kB
> xc_dom_ramdisk_file:
filename="/var/run/xend/boot/boot_ramdisk.2aUKzk"
> xc_dom_malloc_filemap    : 6646 kB
> xc_dom_boot_xen_init: ver 3.1, caps xen-3.0-x86_32p hvm-3.0-x86_32
> hvm-3.0-x86_32p
> xc_dom_parse_image: called
> xc_dom_find_loader: trying ELF-generic loader ... failed
> xc_dom_find_loader: trying multiboot-binary loader ... failed
> xc_dom_core.c:495: panic: xc_dom_find_loader: no loader found
>
> Anyone have any suggestions at all? I essentially just created a new image
> file, used fdisk to create the partition, and installed grub into the mbr,
> then copied the contents of the OS from the old disk image using "cp
-a".
If you''re seeing pygrub then something is going wrong already: if
you''re using
HVM virtualisation then you should be booting /real/ grub.

What does your config file look like?  Most likely you''re missing some
option
needed to kick the guest off in HVM mode.

Cheers,
Mark


-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

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