Bug #14450
closed23.05 fails to boot on Hyper-V after VM power off, workaround
0%
Description
This is an extension of other posts and redmine issues with booting on Hyper-V.
My host:
Windows Server 2022, fully up to date as of May 2023. Hyper-V role installed. AMD Ryzen 5700G, 32GB RAM, Intel 4x10Gbit SFP+ NIC
My VM:
Generation 2, VM Version 10, UEFI Boot, Secure Boot Off, 2 vCPU, 6GB RAM, 20GB VHDX, 1 vNIC (trunked, all vlans) via 1 vSwitch, All integration services offered, No automated checkpoints, all other settings are defaults, except MAC Spoofing is enabled.
pfSense:
23.05. Updated on 5/24/2023. Prior pfSense+ 23.01, updated on 4/24/2023. Prior pfSense CE 2.6, updated on 4/8/2023. Prior pfSense CE 2.5.2, in November 2022.
Reproduce:
Take Hyper-V checkpoint
Upgrade to pfSense 23.05 from 23.01
pfSense downloads, updates, reboots, gets back to UI all seems normal
Take Hyper-V checkpoint again
Halt system (Power Off VM)
Power on VM
Stuck at UEFI screen (see linked forum posts for the screenshot, it's the same)
Roll back via last checkpoint, pfSense is working (it has not been halted from the VM point of view)
Workaround:
Halt or Reboot pfSense
Cold Boot pfSense or pfSense warm boots (same result either way)
pfSense Hangs at UEFI boot screen
Power cycle or Reset VM (same result either way), at pfSense boot screen...
Select Option 8
Select Option 2, then 2 again (cycle from boot option 1->2->1)
Select Option 1
Select Option 1 to boot
pfSense Boots normally
The workaround needs to be manually performed at each boot, otherwise it hangs at the aforementioned UEFI boot screen. It is not necessary to boot into the last image (in my case 23.01), it is only necessary to toggle the boot entry from 1->2->1.
There seems to be something wrong with the boot entry when zfs/default is automatically selected at power-on. Cycling from default (23.05) to the backup (23.01) then back to default fixes the issue; pfSense boots normally.
Based on the notes in redmine #13895, it seems reopening the bug/creating a new bug report is in order.
Sources:
https://redmine.pfsense.org/issues/13895
https://redmine.pfsense.org/issues/13875
https://forum.netgate.com/topic/180336/23-05-fails-to-boot-on-hyper-v-after-vm-power-off-workaround
https://forum.netgate.com/topic/176572/hyper-v-upgrade-from-22-05-to-23-01-b-20221217-1429-fails-to-boot
https://forum.netgate.com/topic/176778/pfsense-refuses-to-boot-on-hyper-v
Relate
Updated by Marcos M over 1 year ago
- Category changed from FreeBSD to Operating System
- Status changed from New to Rejected
Currently 23.01 is a required step in this situation, hence there's no way to avoid the issue. Once it's possible to update directly to 23.05, this shouldn't be an issue.
Updated by Travis McMurry over 1 year ago
Had root cause been identified? Are there known manual repair steps? As of 6/11 there are no 23.05 patches available.
Any info on problem/solution would be helpful. We've had to pause automated windows updates until pfSense can get sorted out.
Updated by Kris Phillips over 1 year ago
pfSense Plus 23.05 direct upgrade from CE should now be available, so this should be no longer an issue. Can you please test?