pfSense 2.7.2 in Hyper-V freezing with no crash report after reboot

jacolex

@maitops yes, since 10 days. I also disabled hn ALTQ support (no clue if it's necessary). Observing kernel hvevents, no issues. But I have to wait 2-3 months to say, that it's stable.

jacolex

@maitops unfortunately, today morning we encountered network outages and the firewall needs to be restarted.

stephenw10

@Bismarck said in pfSense 2.7.2 in Hyper-V freezing with no crash report after reboot:

No hvevent storm here for 6 days and 23.5 hours since my last update,

So this was setting the power management to 'high power' in Hyper-V? Which presumably disables throttling down the VM in some way.

Bismarck

@stephenw10

Yes, or just disabling the power management/green feature of the Nic should be enough, this is how it is right now on my Hyper-V host. There was a message (no error) in the Windows event logs about switching states or so, while the hvevent storm.

maitops

This post is deleted!

Bismarck

Quick update:

Had to reboot once because auf updates, but since than rock solid no incidence. Enabled all extra IP-Lists and Suricata and so again.

@maitops Just disable all energy saving features of the nic or select high performance power profile in windows for a test.

It must be the power state switching or the system tunables I did im my last update post.

maitops

@Bismarck I still have the issue, I have a mellanox connectx-6 Lx NIC, I just disabled the "Interupt Moderation" too

Bismarck

@maitops

I have a Intel 82599 and X550-AT2 in use.

Did you try the loader.conf.local and system tunables from the screenshot?

maitops

@Bismarck Yes, iI changed the loader.conf and rebooted.
the tunable, not everything, only:

hw.hvtimesync.sample_thresh
hw.hvtimesync.ignore_sync

i can try to set all the others too

stephenw10

You should set custom loader values in /boot/loader.conf.local (create that file) to prevent them being overwritten by the system.

shoulders

is this the same underlying issue as

https://forum.netgate.com/topic/197248/pfsense-2-7-2-ram-leak-wired-memory-pool/11

might be irrelevant it is on a hypervisor.

solution looks like it might to update to pfsense 2.8.0

maitops

@stephenw10 My bad, i'm trying with this.
I will tell you if it solved my issue.