Regression #14773
closed
Unable to boot pfSense after installation on Proxmox VE 8.x
0%
Description
I have multiple new pfSense 2.7 installations that are unable to boot after installation. Also tested with pfSense 23.05.01, with the same issue. The pfSense instances are virtualized on Proxmox VE 8. They are running as q35 maskines with OVMF (UEFI), as described in the documentation here: https://docs.netgate.com/pfsense/en/latest/recipes/virtualize-proxmox-ve.html. Secure boot is disabled. It seems like some kind of a race condition. The router is able to start correctly appx 1 in 100 tries.
Some mentions of similar issue here https://www.reddit.com/r/PFSENSE/comments/11b5pj7/2301_upgrade_wont_boot_freezes_at_efi_framebuffer/ and https://forum.netgate.com/topic/177220/latest-pfsense-23-01-beta-freezes-on-hyper-v/62.
Files
Related issues
Updated by Christopher de Haas 8 months ago
Also found this redmine issue which may be related https://redmine.pfsense.org/issues/13895
Updated by Jim Pingle 8 months ago
- Tracker changed from Bug to Regression
- Subject changed from pfSense unable to boot on Proxmox/KVM to Unable to boot pfSense after installation on Proxmox VE 8.x
- Priority changed from Urgent to Normal
It works fine in Proxmox VE 7.x, so something must have changed in 8.x, so there is only so much we can do there. It may be an issue that Proxmox VE needs to correct on their side.
My Proxmox VE nodes are all still on 7.4 and have no trouble booting.
The links you posted for Hyper-V and so on are likely unrelated. Similar, but not the same issue.
Does it work with legacy BIOS booting instead of EFI?
Are you using UFS or ZFS?
What type of partition/booting setup did you choose in the installer?
Updated by Christopher de Haas 8 months ago
The systems were installed using ZFS. Following your suggestion here https://forum.netgate.com/topic/182742/pfsense-2-7-unable-to-boot-on-proxmox/8 I have tried to change the CPU type. All the systems were using host CPU type (which in this case is a Xeon D-2187NT). I have now tried with kvm64 and x86-64-v2-AES types. So far it seems they all boot reliably with either of these types. The boot issue with host CPU type still seems like a bug to me, but at least it is not blocking anymore.
Updated by Jim Pingle 8 months ago
- Status changed from New to Not a Bug
Thanks for following up.
We have seen some similar reports in the past but they were all issues with the Hypervisor kernel and/or hardware BIOS/CPU microcode.
In other words, things beyond our control as a VM guest.
It's possible that it is already fixed upstream (or will be soon) for your hardware eventually with a kernel update from Proxmox VE or similar. Check with the OEM for BIOS updates and check in PVE for kernel updates.
Updated by Marcos M 2 months ago
- Related to Bug #15165: Early boot hangs on pfSense CE added
Updated by Steve Wheeler 9 days ago
This is still an issue in 24.03. See: https://forum.netgate.com/topic/187667/uefi-vm-upgrade-failure