Uefi Servers do not boot after V2V to AHV using Move 3.3.1 | Nutanix Community
Skip to main content

Hello all,

05 months ago, I faced from some difficulties to perform P2V to AHV for UeFi servers : I performed P2V using VMware Converter to migrate to an ESXi server; and after I used “move” to migrate to AHV. 

While booting the VM, I saw a black screen and nothing else appeared on the screen.

As I said above, it happened 05 months ago; At this time, Nutanix did not support migration of Uefi servers yet.

Since the release of AOS5.11 and Move 3.3, Nutanix supports the migration of Uefi servers (As explained in the release notes).

So I migrated AOS to the latest version (5.11.1) and used Move 3.3.1 to perform migrations of 03 servers that use Uefi.

In spite of that, the VMs displays nothing while booting...even if I wait for several minutes, I get nothing.

In PRISM, I switched the boot mode to BIOS and after to Uefi, but I got the same results.

In vCenter, I switched the boot mode to BIOS before performing migration. After Migration (using Move 3.3.1), the results are the same. 

Could you help me fix this issue ? Are there some explanations or tips for that ?

Thanks in advance.

I can say that we have moved around 50 or so uefi boot vms from hyper v to ahv with no issues however I did experience something similar to this when the virtio drivers were installed but somehow corrupted. I had to do a manual uninstall and reinstall. 


Sorry its not clear to me if you get the UEFI boot screen?
It is very clear before its trying to boot the OS if you successfully got the boot method changed.
If not maybe its not yet implemented properly in the GUI (often happens in their first try) and you still need to do the through cli.

nutanix@cvm$ acli vm.update vm uefi_boot=True


Hello Ananix,

Indeed, I can see the UeFi boot screen, but after the black screen appears and nothing else appears on the screen.

I also changed the boot mode in acli with the command “acli vm.update vm uefi_boot=True”, but after, I got the same result.

Are there some other tasks to perform when the Uefi boot screen appears ?

Thanks.


@angeessan nope, the next thing to do is to make sure your truly do follow the uefi standard or have some odd implementation of it.
I have had to drop the vendors implementation and create it by hand myself from the UEFI documentation, then boot it from other media and recreate the system files.
But to begin with you can go into the UEFI menu and browse the disks to see if you can even find the files you need, if so try and call them by hand from the menu. If that is possible I would try and see if you could manually tell UEFI to use them or try and figure out why it does not just use them. Maybe you have more than you think when browsing through or something else will become clear in the process.
Good luck.


@angeessan oh by they way i think at one point you had to use a special naming scheme for you files, i cant remember if i had to do that last time or if the implementation have become better.
I found this note… rename /boot/efi/EFI/ubuntu to /boot/efi/EFI/boot


Hello @ananix,

 

Thanks for your replies.

I will check the UeFi and revert you back.

Thanks.


Hi, @angeessan 

Just to get more information and add some knowledge here.

Have you verified that the virtual machine is in the compatibility matrix for UEFI Supported VMs?

https://portal.nutanix.com/#/page/docs/details?targetId=AHV-Admin-Guide-v511:vmm-compatibility-matrix-for-uefi-supported-vm-r.html

Hope this helps!
 


Hi @HITESH0801,

 

You may be right, because the related OS is Windows Server 2008 R2, and is not in the matrix.

I am very surprised that a very few number of OSes are in the matrix…

Thanks a lot.