Yeah, it depends on how many VMs you need to spin up. If you're just doing a few then Expert install is definitely the way to go. The more you do, the more taking the time to craft a preseed file will pay for itself.d-i preseed? Not for the casual user then. But just use expert install, surely that's easier than mounting then copying an ios , changing the preseed file and then generating a new iso.
Yes, as there is no sign of any change in the bhyve UEFI firmware. So, UEFI boot method has no emulation of storing nvram variables, hence need to fix some linux installs one way or another. UEFI-CSM boot method has no fix to work with VNC, hence need to use/generate linux iso that will install over a serial console. BETA3 now works with UEFI-CSM using the right iso and the correct device order settings.Oh I'm confusing the issues, sorry. Thanks Kris.
When you say 'limitations' is this a long term thing then?
For Debian 9 use expert install and answer "YES" when ask to "Force grub-efi installation to the removable media path". Or, post install don't try copying files around, just use this command:OK. So, I have been attempting the prescribed fix for VM boot problems, in my case on Debian stretch. Creating the directories and copying the efi file do not result in boot - still stops with the EFI manager.
I was looking for any updates or idea when to expect a fix. Is there somewhere this is being tracked? Or do I bail on Debian for CentOs or other distribution for my VMs ?
grub-install --efi-directory=/boot/efi --boot-directory=/boot --removable
Failed to set MokListRT: Invalid Parameter Something has gone seriously wrong: import_mok_state() failed: Invalid Parameter
cp /boot/efi/EFI/centos/grubx64.efi /boot/efi/EFI/BOOT/BOOTX64.EFI sync;sync;sync poweroff
VNC works just fine in my case, if you have multiple network interfaces configured it might not pick the one you are logged into the UI.So, the UEFI-CSM was supposed to make it a BIOS like environment. However, when installing Centos 7 I can't do the Web VNC to do the install. How are we supposed to get the console for the VM if it's not UEFI?
My bad, I mostly don't care about secure boot and didn't know the original source of the problem. At least it's a good exercise for the beginners, gets them used to booting into rescue :D
Failed to set MokListRT: Invalid Parameter Something has gone seriously wrong: import_mok_state() failed : Invalid Parameter
I've seen this post, but I can't even get to the part of booting into that troubleshooting because the serial console from the GUI does nothing and neither does looking via VNC. I simply can't even install the OS on this dumb empty disk...
Don't use the latest Centos 7 1810 minimal. Pick an earlier iso and upgrade following the advice at: https://bugs.centos.org/view.php?id=15522I've seen this post, but I can't even get to the part of booting into that troubleshooting because the serial console from the GUI does nothing and neither does looking via VNC. I simply can't even install the OS on this dumb empty disk...
So it's a CentOS issue. If you a CentOS 1503-1 the install will be fine. BUT! If you do an update it craps out again. I'm looking into what package is actually mucking things up. There's also a post on the CentOS forum that is going over the same issue. It's something related to using "VM" EFI because CentOS is looking for the "hardware" to support EFI and doesn't find it since the VM EFI and Hardware EFI are the same but different. Also if you try to use the CentOS ISOs after 1503 you get the same thing. Some are a little different but due to the same thing.Thank you very much, I missed the part of installing an older machine first. Wow this is tricky, let's hope not everything on FreeNAS requires you to troubleshoot the hell out of it :D
After further research I'd have to agree.It's Centos's fault actually -_-