very-undude
commented
2 years ago The EFI boot menu is a whole different beast than the BIOS boot menu. There is no code shared between the two. Also, templates of OS-es that do not have EFI implemented will not be listed in the menu.
I found a problem with the subtemplates menu not being rendered correctly, but I could not find the problem behind the empty boot menu you are experiencing.
I have some questions for you:
-
Are you sure you have templates that are supposed to show in the menu? Remember e.g. Debian linux will not show, since EFI is not implemented for that OS. Only ESX 5,6,7, Windows 7+ and Redhat/Centos 7+8 have EFI booting implemented at this point.
-
What do you mean with 'even though I previously had menu options configured'? Did you manually log into the appliance via a terminal session and setup an EFI boot menu?
I created a development Patch 3. Can you try that? It should fix the subtemplate menu problem and do more extensive logging to the /var/public/log/ipxe.log file when it renders the EFI boot menu. Please let me know what the logfile says in your case (after installing the patch and booting from EFI).
https://github.com/very-undude/ultimatedeployment/blob/dev/patches/uda30P3.tgz
Please let me know what you found
scottythefreak
From Scott Truman at Youtube:
Hi, not sure where the best place to chat with you is. But, is there anything special we need to do after we patch? I booted from a VM with EFI and get an empty "UDA boot menu" where the only option is the "Exit iPXE and continue BIOS boot", even though I previously had menu options configured. If I go back to boot from BIOS I see the menu with options as before...