EFI Boot

[Parallels User]

>>> Message has been deleted by the user <<<

 

[mmika]

At VM configuration menu choose "Boot Order" element and in a drop-down field "Advanced Settings" add a string "vm.bios.efi=64"

 

[Parallels User]

>>> Message has been deleted by the user <<<

 

[mmika]

1. There is no EFI system partition with FAT on a virtual disk
2. There is no EFI loader file called EFI\BOOT\bootx64.efi

Try to locate it manually selecting "Boot Maintenance Manager" -> "Boot From File"
Also it would be helpful if you provide a screenshot of this window called "File Explorer" if you won't be able to locate EFI loader.
In common case you shall press on entry "EFISECTOR", [PciRoot(0x0)/Pci(0, 0x1F, XXX)/{Ide,Scsi,Sata,NVMe}/HD(X,GPT,XXXX], then "EFI", then "Boot", then "bootx64.efi"

It would be more helpful if you choose "Send Technical Data" and share its ID. At this moment I know nothing about VM you trying to start: how many disks, what guest OS and so on.

 

[Parallels User]

>>> Message has been deleted by the user <<<

 

[mmika]

Hmm. You do have a bootcamp based VM. How bootcamp data was moved to new MAC?
Is native bootcamp able to boot?

 

[Parallels User]

>>> Message has been deleted by the user <<<

 

[mmika]

I would suggest to remove Bootcamp VM (only VM configuration will be removed), then import bootcamp again.

 

[Parallels User]

>>> Message has been deleted by the user <<<

 

[GampaA@P]

Hi, please refer to the knowledge base article to fix the error EFI Boot on Parallels Desktop.

 

[wwh1]

There is another test probably you can try. I had to use Lagecy BIOS as well but found adding "vm.bios.efi=64" in Boot Flags did not work. I tried to open the .pvm fold and locate to config.pvs. You can find "<EfiEnabled>" label in that xml file and change it from 1 to 0. Then probably you can get the legacy BIOS without EFI.
I'm a Paralles user so this is not an official response. You will take your own risk.