Victor Sudakov wrote: > > Has anyone tried to run FreePBX under bhyve? That's what I get trying to > start the vm after a successful automatic install from the ISO image: > > Boot Failed. EFI DVD/CDROM > Failed to set MokListRT: Invalid Parameter > Failed to open \EFI\BOOT\grubx64.efi - Not Found > Failed to load image \EFI\BOOT\grubx64.efi: Not Found > start_image() returned Not Found > Boot Failed. EFI Misc Device
Below are the partitions the automatic installer has created (looking at
them from another vm):
root@mfsbsd:~ # gpart show vtbd1
=> 34 41942973 vtbd1 GPT (20G)
34 2014 - free - (1.0M)
2048 186368 1 efi (91M)
188416 4096000 2 ms-basic-data (2.0G)
4284416 37654528 3 linux-lvm (18G)
41938944 4063 - free - (2.0M)
If I "mount_msdosfs /dev/vtbd1p1 /mnt/" I see that grubx64.efi is not
where bhyve expects to find it:
root@mfsbsd:~ # find /mnt/ -name grubx64.efi
/mnt/EFI/centos/grubx64.efi
Who is to blame, bhyve or FreePBX's installer?
How can I tell bhyve's UEFI loader to look for grubx64.efi in a
different place? Or look for a different loader?
Who says that the image to load should be "\EFI\BOOT\grubx64.efi" and
not "\EFI\BOOT\BOOTX64.EFI" for example?
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/
signature.asc
Description: PGP signature
