installer: switch to bsdinstall to bring compatibility with Hyper-V Gen2

[Schroeffu]

The installer does freeze at the step "Select Task: Guided installation, Manual installation, Import configuration, Reset password, Reboot, Exit".

Version: OPNsense-18.7-OpenSSL-dvd-amd64.iso
Happens on: Hyper-V
Hyper-V VM: Generation 2, Secure Boot disabled

Screenshot: https://imgur.com/a/rSNq4qz

I have already tried the idea from https://forum.opnsense.org/index.php?topic=4470.msg17105#msg17105 to add set kern.vty="vt" and set console="efi" while booting - still freezing. I also tried set kern.vty=sc but the its not booting anymore with exactly the same issue like here screenshoted: https://github.com/opnsense/core/issues/2254#issuecomment-382223999

I'am opening an issue here, because i really want to compare pfsense <> opnsense. pfsense was install-able on the very same hyper-v host without any issue, so, something is different to opnsense causing the issue. Sorry, there are no logs, its just freezing.

See also https://github.com/opnsense/core/issues/2254#issuecomment-372104272 , according to the comments there after closing the issue, other poeple are affected too.

[fichtner]

This is Gen2, right? We've been talking about this for a while. The frontend of the installer freezes, but the backend is still there. Try CTRL+C and log into the installer again and it should continue where it left off?

[Schroeffu]

Yes Gen2. You are right, entering CRTL+C and log-in again is workaround. At the point "Choose UEFI/MBR" mode it logs me out again. CRTL-C + relogin again was working. Great!

Now just my working colleagues got immediately IPs from OpenSense's DNS DHCP , aargh.. Had to stop the fresh install immediately again, but it was looking OK.

Anyway, I think with your fanstatic workaround its ok to install it on Hyper-V , thanks again!

[fichtner]

LAN and WAN interfaces might be reversed?

I'll look into the installer stability on Hyper-V for 19.1 further to hopefully fix it and bring it in line with how it works in all other HW and VM environments. :)

[Schroeffu]

LAN and WAN interfaces might be reversed?

I'll look into the installer stability on Hyper-V for 19.1 further to hopefully fix it and bring it in line with how it works in all other HW and VM environments. :)

My fault, I meant DHCP (not DNS), OpnSense was giving immediately ips to other clients but it shouldn't, will check in an OpnSense Forum for help how to deactivate DHCP during installation of OpnSense.

Thanks for tracking the issue about this Hyper-V freeze.

[soder10]

@Schroeffu: try assigning a new Hyperv vSWITCH to your testing VM, that has no access to your prod. LAN, before rolling out any such trial VM into production. Any non-planned DHCP is dangerous to a prod network.

[fichtner]

(using this to track the hyper-v issue now since I couldn't find an active ticket)

[fichtner]

Good news everyone! I found a way to reproduce a segfault while working on ZFS support for the installer... opnsense/bsdinstaller@058fccb9f911

I can upload an image in a few days for the Hyper-V savvy to test it. :)

[fichtner]

A test image should be available later today... sorry for the delay.

[fichtner]

Here it is, please test :)

https://pkg.opnsense.org/FreeBSD:11:amd64/snapshots/OPNsense-201901021629-LibreSSL-dvd-amd64.iso.bz2

(image contains an intermediate state between 18.7.9 and 18.7.10 but should work fine in production including updates if required, but is not overly recommended)

[marjohn56]

Still the same, hangs ( or appears to ) at the Guided Install. CTRL C drops to prompt and restart installer then works,

[fichtner]

So the segfault is a different issue. Can you post /tmp/installer.log from when it hang (don't restart)? The hang is specific to Hyper-V for some reason... and when you "restart" does it stay in the crashed menu or does the navigation restart?

[fichtner]

another thing--- can you try the same with the early installer ?

When it prompts for "import" press enter, then type "!" and press enter. In the magic shell, type "opnsense-installer" and enter...

[marjohn56]

Early installer freezes at 'OK Lets Go' & I cannot break out of it.

In normal install I get to 'Accept these settings' and that's it, I can however then hit CTRL-C and break out. Log in again and away it will go and install. Now there's another thing I have discovered. If go for manual install then it gets as far as Edit Partitions, then freezes and it's eating CPU, so much that my cooler pump and fans go into overdrive. Again, CTRL-C will break out of it.

I've not configured the virtual switches yet on Hyper-v so cannot pull the log, I have however grabbed it and have some images for you. In order

[marjohn56]

Ok, had a few minutes to spare before zzzz.

Here's the installer log. I CTRL c'd and then logged in again and it worked, I'm sure you'll see that in the log.
installer.log

[marjohn56]

Here's one that I did not hit ctrl-c on. just left it and grabbed the log.
installer_no_ctrl_c.log

[bugz8unny69]

I might be able to lend a hand with this but the issue, the logs doesn't explain a lot for a passer by. The differences, is DFUI? Only people who are familiar can help :(

[bugz8unny69]

For more context, I've come across a few people on the forums who are kvm based are experiencing 'random' refreezes. So far, I haven't changed CPU model on KVM side, I plan to test to using host-passthrough.

[fichtner]

Are we talking about installer "freezes" or system freezes? To me it seems the only way the installer freezes is when their local TCP traffic is dropped for some reason, hence the "pfctl -d" question.

This, however, has no association with freezes as the installer only appears to be frozen but the system (and backend) remains responsive. And this is only the case for Hyper-V.

[bugz8unny69]

Ahh, right, forgot. Sorry.

[fichtner]

No worries.

[bugz8unny69]

I watching a lot open source communities, I should have read up on this issue! I matched this problem with a freezes

[smoonlee]

This is still an issue in 19.1 iso?
trying to build this Windows 10 1709 and still freezes and then when i try the Ctrl + C Method and log back in it just restarts the installer.

[fichtner]

Yes.

Also when you log in as root, option 8, using "opnsense-installer" ?

[smoonlee]

Yes.

Also when you log in as root, option 8, using "opnsense-installer" ?

Ok, Let me try this

[smoonlee]

Same issue, freezes on the Select Task Option and Ctrl + C and relaunch started the install process from the beginning.

[fichtner]

It would mean the backend dies a horrible death, is this in dmesg ? There's also /tmp/installer.log

[Schroeffu]

Hi there, something has changed between 19.1 <> 18.7 installer? (OPNsense-19.1-OpenSSL-dvd-amd64.iso)

The workaround from 18.7 is not working anymore for me, CRTL + C while freezed installer is with 19.1 also killing the whole install-process, not only "minimize" the frozen installer.

So, the installer starts prompting from the beginning again after CRTL+C & re-login as "installer/opnsense", and it freezes anytime again while asking for Swap Partition. Endless loop for me.

So, could not install 19.1 on HyperV Gen2 so far :-/

[fichtner]

CTRL+C should work again on 19.1.4 -- images will be available next week. Don't expect miracles just yet.

[Schroeffu]

CTRL+C should work again on 19.1.4 -- images will be available next week. Don't expect miracles just yet.

Thank you very much. Where will those images be download able? Official mirror list (can only find 19.1 from january 2019) or somewhere seperately?

[fichtner]

There will be an announcement when 19.1.4 images are out, hopefully on Friday. Still a bit of work to do. :)

[Schroeffu]

Yey, 19.1.4 images are out, I could install OpnSense 19.1.4 on Hyper-V Gen2 again with the workaround, re-login after CRTL+C when installer is freezing. thanks so far.

[kevin-j-morse]

Any progress on getting this fixed? At the very least it would be good to add a warning for Hyper-V users somewhere (maybe docs?) so they don't give up and switch to another distro.

[martingruening]

BTW the same happens on VMware ESXi 6.7 U1, Ctrl-C helps to restart the install

[MysticRyuujin]

So, I'm still getting this issue under Hyper-V as well, but CTRL+C does nothing. Using the 20.1 iso...

Edit; After more tries, I was able to get the CTRL+C to work...

2nd Edit: Sometimes this works, sometimes it doesn't and it's incredibly frustrating. Sometimes it just stops working after hitting CTRL+C and typing the word installer... once it stopped accepting input while typing the root passwords at the end of the installer...

[liv3010m]

I had the exact same symptoms when trying to install OPNsense 20.1 over Bhyve on SmartOS, the Ctrl+C trick worked as advised.

[ntinti]

Same here with bhyve and opnsense 20.1 on FreeBSD 12.1

[fichtner]

Version 0.4 works fine now. Adding more polish as testing progresses, but no reason to keep this open.

[backerman]

Still seems to be an issue when installing on XCP-ng in UEFI mode - ctrl-C, re-login workaround works. (Which has to be done at guided/manual choice and swap partition confirmation.)

[fichtner]

@backerman the installer was replaced in 21.1.5 and this issue was fixed. You cannot, however, use the new installer before a new image is released (21.7 is the next one).