error no kernel found

raxa04

Hello,
I'm trying to migrate vm from an old linux xen server 4.4 to a new server and use the xen2xcp (https://github.com/xcp-ng/xen2xcp) script provided for that. I've also copied the vmlinuz and initrd into /boot/gest.
But when I start the vm, it refuses with the error :

xcp-ngFailed: Internal error: xenopsd internal error: VM = 6813d025-efa3-e52a-6069-d6defaba14f7; domid = 2; Bootloader.Bad_error No kernel found in

So I guess the vm don't recognize the kernel and ram disk but why ? and how to fix it ?

TeddyAstie

Hello,

You can try to convert the offending VM to HVM mode to avoid having to use PV boot (which is not really supported anymore in XCP-ng 8.3).

raxa04

@TeddyAstie thx a lot,
apart from installing grub on the disk, is there anything else to do ?

olivierlambert

No, as long as you have Grub installed and the right boot sector configured, that's it

raxa04

Ok so after a long week on other problems I can get back to my migration issue.
I'm trying to boot from a live environment to add grub, but it just plain tell me that there is no bootable device...

olivierlambert

Enable the "boot flag" option in the table

raxa04

still doesnt want to boot with ether two of the disk or bath check as bootable
from what I know of the disk with my previous try, it just a partition without anything, not even a mrb.

Davidj 0

@raxa04
What's at the top of the Advanced tab for this VM?

raxa04

@Davidj-0

Davidj 0

@raxa04
You should follow @TeddyAstie's recommendation. To do that, click on "Convert to HVM".

raxa04

welp,
I converted the vm to hvm, manage to install grub by copping the migrated disk into another disk with a partition table, then install grub2 by mount it then chroot into it.
When I boot in hvm I land into the bios with no bootable device,
When I convert the vm back to pv I get the error

INTERNAL_ERROR(xenopsd internal error: Domain.Domain_build_pre_failed("Calling 'shadow_allocation_set 51 MiB' failed: Xenctrl.Error(\"22: Invalid argument\")"))

so I'm back to square one

raxa04

ok, so I was wrong, the vm boot ! But as you can see I now have a strange space collision, any idea ?

when I boot in recovery mode, I can get into linux, so I know it almost work.