[SOLVED] 17.1 install on Hyper-V does not see the HD, 16.7 does

[GurliGebis]

Just tried installing 17.1 on a new Hyper-V virtual machine, but it does not see the IDE disk.

Installing 16.7 works fine - I'll be testing if it works after upgrading in a few minutes.

[weust]

Same issue as here? https://forum.opnsense.org/index.php?topic=4395.0

What Hyper-V version are you running? Don't make it a Gen 2, because FreeBSD doesn't have support for it.
Make it a Gen 1, and it should boot just fine.

[GurliGebis]

I know generation 2 doesn't work :)

It is a generation 1 - like I say, it works fine with 16.7 - upgrading from 16.7 to 17.1 breaks it just like in that thread.

[GurliGebis]

Seems like the fix is here, we just need it applied and a new ISO: https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175166&action=diff

[GurliGebis]

With the help from fitch, the problem has been located - here is an ISO to use for installation, if you have the same issue: https://pkg.opnsense.org/snapshots/OPNsense-17.1-HyperV-cdrom-amd64.iso.bz2

[weust]

Ah, great. Will check it out tonight.

[franco]

We'll shuffle this into 17.1.1. :)

[mcmahoc]

Hi,

Just joined the forum as I found this which helped me get 17.1 up and running and hope this helps others.

If you remove MS update KB3172614 or KB3179574 you can resume a faulting 17.1 upgrade. Once the upgrade completes if you perform another update 17.1.1 will install, after this completes you can reinstall the offending MS updates.

Got this from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212721


Thanks,
Chris

[franco]

Hi Chris,

Thanks for the heads-up. :)

We do have a working image for Hyper-V here:

https://pkg.opnsense.org/snapshots/OPNsense-17.1.1-OpenSSL-cdrom-amd64.iso.bz2

And we will fix up the 17.1 upgrade path in a day or two as soon as we know 17.1.1 is working out well on Hyper-V.


Cheers,
Franco

[Aergan]

Thanks - just encountered this now as my upgrade from 16.7 failed yesterday not being able to locate a rootfs.
Going to give this a go shortly

[franco]

Aergan, when you are on 16.7.14_2, you can do:

# opnsense-update -ur 17.1.1
# /usr/local/etc/rc.reboot

If this works for you too, I'll fix the upgrade path for everyone else so instead of upgrading to 17.1 people will go directly to 17.1.1 avoiding the Hyper-V issue.


Thanks,
Franco

[GurliGebis]

I can confirm the 16.7 to 17.1.1 path works on Hyper-V 2012 R2 :)

[Aergan]

Thanks franco. I've decided to do a new installation alongside my existing 16.7 deployment then swap over once I'm happy with the setup & done some testing.
17.1.1 does indeed fix the storage issue - many thanks :)

[franco]

Alright, thanks!

[impvision]

One more issue with Hyper-V:

1. After install v17.1 needs to use menu case 3.
2. Enter command - set hw.ata.disk_enable="1" (/boot/loader.conf)
3. After that enter - boot
4. All will be allright, but ... next shutdown and you need to make these things one more time.

NB! Only shutdown and network adapters movements reset config changes to default.

If you once config this firewall and save state it works perfectly.