Show Posts
1
19.1 Legacy Series / Re: VM of OPNsense on Hyper-V Win Svr 2019 Std - Fails
« on: June 12, 2019, 12:24:53 pm »
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!
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!