pfSense as VM > Stopped at kdb_enter+0x32
-
Stopped at kdb_enter+0x32 -
Moved from Installation and Upgrades by
jimp
-
What kind of Hypervisor? What VM settings?
Usually a panic in a VM means the hypervisor settings and/or VM hardware config/version are wrong for the new guest OS version.
We see that happen more on ESX than others, but usually it's just a matter of making sure ESX is up to date, updating the hardware version of the VM, and ensuring it has the proper version of FreeBSD selected in the VM settings.
-
its hosted on a cloud hoster. the hoster is using proxmox what i know
-
no one with the same problem here?
-
When running pfSense as a virtual machine, it is possible to encounter the error "Stopped at kdb_enter+0x32." This error message indicates that the system has encountered a kernel debugger breakpoint, which can occur for a variety of reasons.
One possible cause of this error is a hardware or software compatibility issue. To troubleshoot this, you can try updating your virtualization software or hypervisor, as well as the virtual machine's firmware and drivers. die Portaloffice-Ressourcen finden Sie hier.
Additionally, you can try disabling any virtual hardware devices that are not required for the pfSense instance to function. -
the system is hosted in the cloud, with proxmox i think. so maybe its related to my cloud hoster then?
-
@opit-gmbh
Did this pfSense ever run in this VM?Which version?
-
@viragomann
yes, it was running with the latest Stable 22.0.5 -
@opit-gmbh said in pfSense as VM > Stopped at kdb_enter+0x32:
@viragomann
yes, it was running with the latest Stable 22.0.5That is a good hint that the problem may be an incompatibility between your hypervisor and FreeBSD 14-CURRENT. pfSense 22.05 was running on FreeBSD 12.3-STABLE. You might want to get with your cloud provider's tech support to see if FreeBSD 14-CURRENT is supported in the environment. Some changes to the VM configuration might be required.
-
my hoster chaned something in the Backend, all good now THX
-
Do you know what they changed? It would be nice to know in case someone else hits this.
