PFSense VM not getting pass autoboot countdown in 8.3beta 12/21/2023 update.
-
Hello all,
Not sure it this is something specific to this update on (8.3beta 12/21/2023 release update) or not but did anyone else run into pfsense 2.7.1 having the VM not doing the autoboot countdown on startup screen after update? Apparently my node has this problem. I have to manually press the enter button to continue from startup screen...
Unless I accidently change the console keyboard from XOA setting somehow? I always use SSH to do all my stuff but if there is anyway to type in directly from console would be nicer
Screen it is stuck on until enter is pressed.
Reason i suspect it is XCP-ng is because there was no change before xcp-ng update (8.3beta 12/21/2023 release update) and when i revert vm to older version of the snapshot it has same problem. Really weird...
FYI all other VM didn't have this problem as they autoboot up normally.
-
I know this happen to two of my node in a pool. Reinstalling a older 8.3b version before update and testing it. Will let everyone know if after update this issue persists again. Unless all 3 node in the pool have same issues.... which would be rare I would think.
-
Solution
Method 1: Best methods as it revert back to older (run this on each host if there are multiple hosts in a pool)
Run this on host and accept the downgrade.yum downgrade edk2The "edk2" package is related to the UEFI firmware used by the virtualization platform.
@stormi Credit to Stormi for suggesting this.Method 2: Change UEFI to "bios" or "Default (bios)" (Just go with 1 to make your life easier) (Some version of PFSense may not like this method)
Bios or Default (Bios) doesn't have this issue where boot loader get stuck.Method 3: Change boot loader autoboot_delay time
UEFI version of PFSense maybe even FreeBSD will run into boot loader getting stuck. This is what I suspect for now.For those that run into this problem apparently I decided to bypass the boot loader in FreeBSD if I desperately need UEFI. This could be a XCP-ng problem that affect all FreeBSD in general. This could be a issue with XCP-ng and how it handles FreeBSD in the new 8.3beta (12/21/2023 update). But to avoid this for now do the following in terminal:
Add local so that updates doesn't affect the original version and this will only update this one parameter.
vi /boot/loader.conf.localAdd the following:
autoboot_delay="0"Not ideal, as clean install doesn't have this and we will have to do this each time. So will see if anyone has a better suggestion. Beside seeing the boot loader is nice when we want to choose the options presented.
[Yes i update it today and ran into this problem on all my pfsense vm instances and all backup copies that run in 8.3b] I thought my whole pool 3 different host all fail to update properly but I migrate a VM copy to a separate pool and it ran into same issue. Sadly can't downgrade that easily i think...
-
W wilsonqanda referenced this topic on
-
@wilsonqanda @stormi Now, Ubuntu 22 (Linux) boots fine.... FreeBSD 14 gets stuck on the countdown. I'll test the new update when released as I don't need to UEFI boot production 8.3 guests.
-
@Andrew Thanks for confirming that FreeBSD has the problem too. I don't have multiple FreeBSD i can test but i did suspect it might be the case as PFSense is FreeBSD.
-
@wilsonqanda Downgrading the EKD2 package fix it for now, as posted:
yum downgrade edk2-20180522git4b8552d-1.5.1.xcpng8.3