-
Title
“Boot Failed. EFI SCSI Device” error when booting a Hyper-V VM for Hyper-V Generation 2 Linux VM -
Description
After successfully completing a one-time or continuous virtual export to Hyper-V, the virtual machine will not boot and displays "Boot Failed. EFI SCSI Device." in the console window.Further errors include "Failed to open \EFI\BOOT\grubx64.efi - Not found. Failed to load image \EFI\BOOT\grubx64.efi : Not found "Source VM is a generation 2 VM protected agentlessly or using agent.
-
Cause
By default, in generation 2 linux VMs during installation, the EFI firmware will be installed outside the disk (which is the shimx64.efi as shown in boot order). For our backups, this firmware can't be backed up at all and thus after export, this is not present in the exported VM, thus it can't be booted up correctly.
-
Resolution
Knowing the above, there are actually two resolution for this issue -1. After export, reinstall the EFI firmware using the efibootmgr from a linux live CD (either rapidrecovery live cd or original os cd)
efibootmgr --create --label CentOS --disk /dev/sda1 --loader "\EFI\centos\shimx64.efi"
After this, perform a reboot and the VM will be then bootable
2. Ensure EFI is correctly installed to the disk instead of the firmware, this will ensure the virtual export is bootable without any repair needed.
For CentOS 7, on the original server, run this
cp -r /boot/efi/EFI/centos/* /boot/efi/EFI/BOOT/
After this is run, try exporting again, the server will be bootable just fine without the shimx64.efi on hyper-v.Reference Microsoft article (For ubuntu):
Note the above commands are for CentOS 7 and may need to be changed for different Linux OS such as Ubuntu and also if /boot/efi is located in different partitions.