VM of OPNsense on Hyper-V Win Svr 2019 Std - Fails

[tamer]

I'm getting the same kernel panic on ESXi 6.7 (https://forum.opnsense.org/index.php?topic=11419.0).

[bimmerdriver]

I halted the VM, then rebooted it. The update completed and afterwards, the system booted properly.

[bimmerdriver]

After rebooting, I was going to try rebooting again from the gui and I'm getting this error:

OPNsense\Core\HaltController handler class cannot be loaded.

It halted okay from the console.

Reboot seems to be okay.

I rebooted again the problem remained. Seems to be a bug or maybe a left-over from the error during the upgrade.

[neovs]

I also came across this problem on hyper-v and on 2016 and on windows10 help to unblock.
I tried to set it to 0 when loading an error and an eran virtual machine goes out how to bypass the error.
Thank .

[buddwm]

I have the same exact issue using KVM.  I've booted to kernel.old in the meantime until this gets resolved.

[RGijsen]

Is there an update yet from the OPNSense team? Easy to reproduce even on a Windows 10
hyper-V box. Would the next update cover this issue?

[franco]

There's no solution that satisfies everyone yet. The OS kernel version changed and we are stuck with going thorough thousands of changes to find the issue while still fixing bugs and adding features for OPNsense.

Some issues seem to be resolved or worked around easily, but there are already multiple ones for multiple scenarios and we usually start at "won't boot" which makes it harder to see which is which...


Sorry,
Franco

[bunchofreeds]

After reaching the Boot Loader screen,
Pressing ESC to enter the loader Prompt
Enter 'start' which I believe loads the kernel and modules
Enter 'lsmod' which lists all loaded files for verification

Enter 'boot' then fails immediately with 'kernel trap 12 with interrupts disabled' ... etc. error

Maybe this will help someone more knowledgeable than me as to what is causing this?

[RGijsen]

19.1.2 released, I didn't see any changes in this regard in the changelog. However I tried to (after taking snapshots) my test-environment from 18.x to 19.1.2. However, as far as the logs go, I see it first tries to 19.1:

***GOT REQUEST TO UPGRADE: maj***
Fetching packages-19.1-OpenSSL-amd64.tar: ...............................pgrep: Cannot open pidfile `/tmp/opnsense-fetch.pid.oUd52D': No such file or directory
done
Fetching base-19.1-amd64.txz: ........ done
Fetching kernel-19.1-amd64.txz: .... done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Extracting packages-19.1-OpenSSL-amd64.tar... done
Extracting base-19.1-amd64.txz... done
Installing kernel-19.1-amd64.txz... done
Please reboot.
***REBOOT***

19.1.2 update was available in the updates-list though. Would this mean we will have a hard time updating these affected machines to a 19.x version that has this issue fixed later on, as it'll always first update to this non-working version? So maybe offtopic here, but how do we update to a 19.1.x version in this case, skipping the faulty 19.1 release?

[lattera]

If the price is right, I will be looking to acquire a budget-friendly system on which to run Hyper-V. HardenedBSD's budget for this kind of thing would be $500 USD.

Just a quick reminder that HardenedBSD accepts donations, both monetary and hardware. We appreciate all contributions of any kind.

[mimugmail]

A hosted system with full access via VPN wouldnt help?

[RGijsen]

Well, as stated by multiple people, any somehow Windows 10 Pro machine will do, as you can just enable Hyper-V and installing a Gen2 VM with OPNSense shows the same issue. While I expect the issue for Gen2 VM's the same as with UEFI enabled bare-metal hardware, I can't of course not sure of that. HAving said that, it's extremely easy to create an environment that manifestates the issue.

[lattera]

Well, as stated by multiple people, any somehow Windows 10 Pro machine will do, as you can just enable Hyper-V and installing a Gen2 VM with OPNSense shows the same issue. While I expect the issue for Gen2 VM's the same as with UEFI enabled bare-metal hardware, I can't of course not sure of that. HAving said that, it's extremely easy to create an environment that manifestates the issue.

The problem is that all my systems run HardenedBSD. ;P

My employer has lent me a laptop on which I can install the 180 day Windows Server 2019 eval. I'll be working on that today. I hope to have some results to report back within the next week or two.

For full Hyper-V debugging support, I'd need a permanent system. I've set up an Amazon Wishlist for HardenedBSD: https://smile.amazon.com/registry/wishlist/2AKXCIOXYO28N/ref=cm_sw_r_cp_ep_ws_MuDECbATM7CVZ

[peter008]

So you need a 550 €-NUC with an i5 for testing? Really?

[lattera]

So you need a 550 €-NUC with an i5 for testing? Really?

All Core i* CPUs have the SLAT instruction, which Hyper-V requires. The Intel NUC uses Core i* processors.