Hallo,
das Problem hatte ich auch.
Schau dir diesen Thread an
https://forums.freenas.org/index.php?threads/how-to-how-to-boot-linux-vms-using-uefi.54039/
Das hat mir geholfen:
The file
/usr/local/share/uefi-firmware/BHYVE_UEFI.fd provides byve with the firmware to support UEFI guests, this function is based on the OVMF tianocore project which is also used as the basis of VirtualBox's virtual machine UEFI support. The bhyve UEFI firmware conforms to the known “Default Boot Behaviour” and looks for the file
\EFI\BOOT\boot64.efi in the EFI partition of your VM. If it's not present you end up in the EFI shell.
One simple remedy is to create this \EFI\BOOT\boot64.efi file in your VM, which is straight forward once your VM has booted.
But how do you boot your VM if you find yourself in the EFI shell at first? Just type exit at the shell prompt, and in the EFI menu system navigate to "Boot Maintenance Manager" and then select "Boot from file" to locate and select your grubx64.efi file.
As root, cd to the /boot/efi/EFI directory of your VM in order to create the new BOOT directory and copy the existing grubx64.efi to /EFI/BOOT/bootx64.efi. The end result should look like this, using Ubuntu as an example:
root@ubuntu-vm:/boot/efi# tree -L 3 .
.
└── EFI
├── BOOT
│ └── bootx64.efi
└── ubuntu
├── fbx64.efi
├── grub.cfg
├── grubx64.efi
├── mmx64.efi
└── shimx64.efi
3 directories, 6 files
root@ubuntu-vm:/boot/efi#
The file bootx64.efi is a copy of the grubx64.efi in your VM.
NB: If grubx64.efi gets updated you will need to re-create bootx64.efi
