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

Started by bunchofreeds, February 01, 2019, 12:16:07 AM

Previous topic - Next topic
Hyper-V Gen 2
Kernel Panic but at different Address

Hi,

tested on a bare metal system with uefi boot.
This board has no legacy boot option anymore.  :-\
My CPU is an i3-8100T on Fujitsu Mainboard D3633-S.
I also get the "new" kernel panic.

March 08, 2019, 10:12:31 AM #47 Last Edit: March 08, 2019, 10:14:18 AM by RGijsen
2019-03-07_hbsd_11-stable_disc1-02.iso

Server 2019 Hyper-V:



W10 1809 Hyper-V (so pretty much same Windows base, but it does show different addresses):




spare HPe DL360 gen9 (Xeon E5-2630 v4 for what is matters) - UEFI boot (though iLO):



loads extremely slow for some reason, but boots perfectly fine.

If you want me to do specific tests on any of them, just ask.


Quote from: lattera on March 07, 2019, 05:36:49 PM
So, I figured out what's wrong. Now to figure out how to fix it.

[...]

I hope this makes sense. If it doesn't, please let me know. I'll try to explain differently.
Nice troubleshooting. Well done.

Hi,

I'm having the same issue on Hyper-V with Gen2 machines. During the installer phase, I get as far as selecting a virtual hard drive, but the installer interface then hangs when selecting the drive. I'm still able to switch to other VTYs but wasn't able to actually install the OS.
I built a Gen1 machine with the exact same specifications and was able to install OPNsense that way - selecting GPT/UEFI for the disk, so as to boot it with the Gen2 VM (which shared the same VHD). I got the kernel panic described in this post, however escaping at the loader prompt and setting vm.pmap.pti=0 did actually allow me to boot OPNsense 19.1.4! I updated /boot/loader.conf afterwards, changing vm.pmap.pti="1" to vm.pmap.pti="0", and am able to reliably reboot the system without a panic. Hopefully that helps someone else with the same issue.

I actually ran into this issue some time ago when upgrading the OPNsense appliances we have at work to 19.1 - they are all Gen2 VMs, however I initially dismissed it as an oddity with the upgrade process and simply reverted to a snapshot of the installation prior to upgrade (18.7) - wish I'd reported it then as I may have been able to contribute to lattera's fantastic diagnosis work!