On Mon, Sep 27, 2010 at 12:32 PM, Jan Bakuwel
<jan.bakuwel@xxxxxxxxx> wrote:
Hi,
A bit more info on this:
Full extract from /var/log/xen/xend.log for this domU session:
[2010-09-27 05:06:22 8161] DEBUG (__init__:1072) Launching bootloader as
['/usr/bin/pygrub', '--args=root=/dev/xvda1 ro ',
'--output=/var/run/xend/boot/xenbl.10154', '/dev/d/xm.dt2'].
Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
> I've prepared a Ubuntu 10.04 LTS server on a Xen 3.2-1 host running
> Debian Lenny on kernel 2.6.26-2-xen-amd64. The Ubuntu 10.04 domU is
> running a 2.6.32-24-server kernel from the Ubuntu repositories, which is
> (must be :-) ) xen-aware. The domU uses pygrub to boot and it works like
> a charm.
>
> Now I'm trying to deploy this domU on a Xen 3.2-1 host running Debian
> Etch on kernel 2.6.18-6-xen-amd64. When I xm create domU on this system,
> I see the pygrub boot menu but then an error message comes up:
>
> Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
Are you sure that both the hypervisor and userland are the same version (3.2) in both Etch and Lenny?
Ubuntu's default kernel is newer pv_ops kernel, which might not be identified correctly as xen-compatible by old xen userland tools.
Try copying the kernel and initrd to dom0, and boot it (i.e. not using "bootloader", but "kernel", "ramdisk", and "extra"). My guess is it will show the same message.
--
Fajar