Hi, I dont' really know if I should post that here or on OPNsense but it look more related to FreeBSD
I'm running an OPNSense VM latest version using FreeBSD 14.1 (14.1-RELEASE-p6 FreeBSD 14.1-RELEASE-p6 stable/24.7-n267939-fd5bc7f34e1 SMP amd64)
The Hypervisor is Hyper-V under Windows Server 2022 up-to-date.
Sometimes the hvevent related to kernel use 100% of one CPU until the VM is rebooted. This paralyse everything that use this CPU and put our production in a downtime.
There is no patterns in the regularity of thoses issues, it can happen after 12h of uptime or 15 days.
All integration services got disabled from hyper-v just in case, the problem is still there.
Dmesg doesn't show anything particular, the hvevent can be the 1 or the 3.
VM settings are in Gen2 on HyperV everything is in default except on the network card for CARP usage, secure boot is disabled.
Basically the usage of the command "top -aHST" show one of the [kernel{hvevent1}] at 100% WCPU, we have also [kernel{hvevent3}] maybe 0 and 2 does the same thing too.
The hvevent run continuously until the reboot, the longest we had was 300 minutes.
We also tried to disable all Hyperv integrations services from the kernel modules in FreeBSD but we couln't find how.
What tests/logs should I provide to understand more what really happen ?
Thank you in advance
I'm running an OPNSense VM latest version using FreeBSD 14.1 (14.1-RELEASE-p6 FreeBSD 14.1-RELEASE-p6 stable/24.7-n267939-fd5bc7f34e1 SMP amd64)
The Hypervisor is Hyper-V under Windows Server 2022 up-to-date.
Sometimes the hvevent related to kernel use 100% of one CPU until the VM is rebooted. This paralyse everything that use this CPU and put our production in a downtime.
There is no patterns in the regularity of thoses issues, it can happen after 12h of uptime or 15 days.
All integration services got disabled from hyper-v just in case, the problem is still there.
Dmesg doesn't show anything particular, the hvevent can be the 1 or the 3.
VM settings are in Gen2 on HyperV everything is in default except on the network card for CARP usage, secure boot is disabled.
Basically the usage of the command "top -aHST" show one of the [kernel{hvevent1}] at 100% WCPU, we have also [kernel{hvevent3}] maybe 0 and 2 does the same thing too.
The hvevent run continuously until the reboot, the longest we had was 300 minutes.
We also tried to disable all Hyperv integrations services from the kernel modules in FreeBSD but we couln't find how.
What tests/logs should I provide to understand more what really happen ?
Thank you in advance