OPNsense Forum
Archive => 18.1 Legacy Series => Topic started by: DanMc85 on February 02, 2018, 12:02:52 am
-
Figured it would be good to have a thread for those specifically running build 18.1 in a Hyper-V Virtual Machine. In this case using the new Gen 2 support which is included in build 18.1 due to the upgrade to FreeBSD 11.1 as the core.
The first issue I noticed is on a clean install.
The installer launches, allows for selecting Keyboard and Display Type/Font
Hit Enter
Freezes on screen where the Guided Install selection is.
However, it is not actually frozen... CTRL+ALT+Delete will still command a shutdown/reboot.
I noticed a weird workaround... change the font/display selection to a really large font (first or section option if I remember correctly)... then go back and change it to the smaller Thin font option. It will mess up the wallpaper shown on the screen, but the menu options actually work and will install successfully.
- Feel Free to add to this or other issues, fixes, or workarounds for Hyper-V Gen 2 related discoveries. -
-
I noticed this too. But after removing the VM, and creating it the exact same, it went fine.
With the r1 release I had a full crash (meaning I could not Alft-F1 to a different vt) right after the installer would copy the files.
I plan on creating a new VM, since the current one is a test VM (18.1_r1 to r2 to final), and will see how that works out.
-
Just done my first fresh install on hyper-v and had no issues - Just as a comment :)
-
Just done my first fresh install on hyper-v and had no issues - Just as a comment :)
Did you use a Generation 2 VM when you created yours? or was it a Generation 1?
-
Hi All.
Same problem here, but additionally the workaround does not work for me. Installer GUI freezes while switching back font.
Cheers,
BlaCKJaCK
-
Short Update - found here:
https://github.com/opnsense/core/issues/2254
Use the 8x14 font, worked for me.
-
Will the problem described in this thread be resolved in the next release?
-
If somebody is willing to test I can send over an URL with a 19.1-BETA image (DVD?). We're still assembling bits and pieces so there's no public test yet.
-
If you send me the URL, I will test it.
-
If somebody is willing to test I can send over an URL with a 19.1-BETA image (DVD?). We're still assembling bits and pieces so there's no public test yet.
Already tested this, still an issue. If I use guided installation and let it do it's own thing the installer appears to freeze at the formatting/partition stage. If I do a manual installation, I can format, that appears OK, I can skip partition and then to boot blocks, seems OK, in fact I can then apparently complete the install, but on reboot the disk will not boot.
-
If somebody is willing to test I can send over an URL with a 19.1-BETA image (DVD?). We're still assembling bits and pieces so there's no public test yet.
Already tested this, still an issue. If I use guided installation and let it do it's own thing the installer appears to freeze at the formatting/partition stage. If I do a manual installation, I can format, that appears OK, I can skip partition and then to boot blocks, seems OK, in fact I can then apparently complete the install, but on reboot the disk will not boot.
If you're testing on windows 10 hyper-v, it's similar to windows server 2016 hyper-v. I have a windows server 2012R2 server and I will be happy to test on it if that would be of help.
-
Can somebody try this on normally crashing Hyper-V install prior to bootup please?
1. Escape to loader prompt (3)
2. Type: set hw.vga.textmode="0"
3. Type: boot
Thanks,
Franco
-
There's a problem there. You cannot install at all if you leave it to do it's own thing, it just appears to freeze, if you manually install then you can skip the partition bit, if you don't it freezes. So skip partition and write the boot blocks, says it's OK and carries on and installs.
I'll check it now with that option.
-
The question is if it still hangs with the graphics mode forced due to enabling it prior to installation. If it still hangs it's a command not returning from the disk. There is a log at /tmp/installer.log detailing the dispatched backend commands.
Thanks,
Franco
-
/tmp where?
-
Installer system: /tmp/installer.log
Installed system: /var/log/bsdinstaller/installer.log
-
That... appears to work... :)
-
Installer system: /tmp/installer.log
Installed system: /var/log/bsdinstaller/installer.log
Where, I could not access the hard drive, even when I did a manual install at reboot it would just attempt to boot from lan as there was no drive to boot from. :)
now I can.
-
Can somebody try this on normally crashing Hyper-V install prior to bootup please?
1. Escape to loader prompt (3)
2. Type: set hw.vga.textmode="0"
3. Type: boot
Thanks,
Franco
I gave this several attempts and it didn't make any difference. I tried several times using the guided setup with no changes to the configuration. Every time, it hung. I also tried several times using the guided setup after changing the font to 8x14. Every time, it hung. When it "hangs", I can see that the VM is still using CPU, but nothing is happening. Even left for a while, there is no installation progress.
-
Yet its installed on mine. cannot test again now until maybe Sunday.
-
Maybe the difference is because you are using a different version of hyper-v.
-
I noticed there is a newer version of the snapshot, so I downloaded it. There is still no difference.
Whether or not I accept the default font or change it to 8x14 and whether or not I execute the set command, the installer hangs at the prompt to select task. There is no getting past this point. It's not even possible to attempt a manual configuration.
-
I took another stab at the "font" theory, but it doesn't make a difference like you said. Will need to build an Hyper-V test machine to inspect this further. To be continued in the new thread.
Cheers,
Franco