SUSE linux server won't boot after p2v

AdyWanBot · 03-09-2021, 05:54 AM

Morning All,

I used clonezilla to image a suse linux server (version 12 sp3) so I can p2v it on to hyper-v.

After the disk image restore,to hyper-v gen 2 vm, the server boots to the grub screen and then gives an error efi : Failed to lookup EFI memory descriptor for 0x00000000f6cea000, which I beleive is normal, but then carries on to a blank screen.

I've used the suse dvd to get to rescue mode and check the grub2 cfg and /etc/fstab entry and it all looks ok.

I've even tried re-installing grub after chrooting which creates a new grub boot entry and a new entry in the Hyper-v 'firmware' but still no luck.

Any ideas?

jsbjsb001 · 03-09-2021, 09:38 AM

Quote:

Originally Posted by AdyWanBot

Morning All,

I used clonezilla to image a suse linux server (version 12 sp3) so I can p2v it on to hyper-v.

After the disk image restore,to hyper-v gen 2 vm, the server boots to the grub screen and then gives an error efi : Failed to lookup EFI memory descriptor for 0x00000000f6cea000, which I beleive is normal, but then carries on to a blank screen.

I've used the suse dvd to get to rescue mode and check the grub2 cfg and /etc/fstab entry and it all looks ok.

I've even tried re-installing grub after chrooting which creates a new grub boot entry and a new entry in the Hyper-v 'firmware' but still no luck.

Any ideas?

From research I've done, it seems you could try updating the kernel and see if that helps. Particularly since, while SUSE Linux Enterprise Server 12 is still supported, it's a pretty old version that was released in 2014 - the most current version is SUSE Linux Enterprise Server 15. Also, since it's a commercial distribution, you should be paying for support for it, therefore you can contact SUSE to get paid support for it.

https://bbs.archlinux.org/viewtopic.php?id=226803

jefro · 03-09-2021, 04:53 PM

(u)efi issue.

A clone works pretty good on identical hardware. You are moving to some unique hardware from physical.

I don't fully get the p2v part. Did you use an import feature of hyper-v?

jsbjsb001 · 03-11-2021, 01:01 AM

Quote:

Originally Posted by jefro

...
I don't fully get the p2v part. Did you use an import feature of hyper-v?

I assume they are talking about this. A quote from the linked article:

Quote:

Originally Posted by What does Physical To Virtual (P2V) mean?

Physical to virtual (P2V) is the process of converting and migrating a physical computer image into a virtual machine (VM). It allows a physical machine to transform into a VM with the same state, stored data, applications and required system configuration and resources.

Physical to virtual is also known as physical to virtual migration (P2V migration).

jefro · 03-11-2021, 03:05 PM

Wow.

I have used P2V programs for decades.

Why someone would clonezilla it then p2v was my question.

Hyper-V like many of the more advanced VM's have more features than Virtualbox.