Upgrade from version 22.05 straight to 23.05 (Hyper-V error in version 23.01)
-
Hello everybody!
As some people know, unfortunately some people were unable to upgrade to 23.01 using Hyper-V due to the error below.
I would like to know if there is any possibility of skipping version 23.01 straight to version 23.05, since possibly the error in question could have been corrected.
Do I really have to switch hypervisors because of this error?https://forum.netgate.com/topic/177220/latest-pfsense-23-01-beta-freezes-on-hyper-v/62
https://redmine.pfsense.org/issues/13895Any tips?
-
I was running 23.01 on my Hyper-V server just fine. Upgraded to 23.05 today. Still ran fine. On first reboot, it started crashing into a kernel panic on boot up and now does it on every boot.
I have no idea what to do now except try to rebuild and restore from a recent backup.
-
@xpxp2002 That's exactly the thing, I've tried to do a new installation numerous times and I couldn't correct this error.
Including, in the topic I sent above, we were trying to do a reinstallation, but to no avail. -
@Snk My issue appears to be related to SR-IOV. I disabled it on all of my VM NICs on the pfSense VM, and the issue goes away. Re-enable it and it comes back. Maybe something to check in your environment?
I ran SR-IOV VM NICs with 23.01 and 22.05 without anything like this ever happening, so I don't know why it's broken now.
-
@xpxp2002 In my environment I have 2 virtual switches, one with the WAN and the other with my LAN.
I don't know how SR-IOV would affect using it this way.
The problem really lies with netgate, as the history of updates released by it is not known to be good.
In this case, I'm completely stuck, because switching hypervisors due to a bug that wasn't fixed in the initial version is something very complex to do in the environment. -
@Snk I suspect you have a different issue here. But I'm in a similar boat as you as far as hypervisors go. I have an entire environment built around Hyper-V. Cost-wise it makes the most sense as a balance of functionality and what I can afford to put into it, and switching to something else just wouldn't be practical cost- or time-wise.
Personally, I've enjoyed the benefits and convenience of having virtualized pfSense for years. Checkpoints have saved me from breaking configs and requiring lengthy rebuilds and restore from back, and made non-CARP failover a breeze with a replica host.
But more and more, I'm finding that while support for virtualization features have improved in the BSD kernel, it is very flaky and much of it seems untested or "best effort". In other words, if it crashes or doesn't work, you just can't use it and there just don't seem to be enough users reporting issues and testing in Hyper-V to make it reliable. I wouldn't mind contributing myself, but I just don't have time for that anymore like I did when I was younger. I really need something more stable. With that in mind, I'm really leaning toward my next major upgrade at home to be a pair of appliances in an HA CARP config.
-
Believe the Hyper- V boot issue was fixed in 23.05. Problem is we can't get from 2.6 to 23.05 direct yet. https://redmine.pfsense.org/issues/13895
