Hyper-V VM constant 100% CPU Load in 2.4.5
-
It generic and happens to a lot of people.
I had to revert to 2.4.4p3 and it stays that way for now. Something i very broken.
Neither pfblocker and ntpd is the culprit here....
-
put all the nuclei exmplo 6 nucles and 6 threads, resolvable my problem was not giving 100 percent of processing and did not force the other virutias machines
-
upgraded on hyper-v 2016 server vm gen2, zfs root from 2.4.4p2 to 2.4.5, i keep getting high cpu and non-responsive gui and network for 1-2 minutes, then a small active/working period 10-30 seconds, then another outage for 1-2 mins. over and over.
-
All my issues actually went away by doing clean install from ISO. Factory reset wasn't enough to eliminate the issue on 2.4.5 after upgrade. I clean installed 2.4.5 from iso, imported config, now i don't see any 100% spikes on my 4-core hyper-v gen2 zfs pfsense vms.
I wrote up all my findings on the issue here, I think its the same problem this thread is discussing:
https://forum.netgate.com/topic/149595/2-4-5-a-20200110-1421-and-earlier-high-cpu-usage-from-pfctl/25Although I see you mention a fresh install also has the issue in your case. In my situations only upgraded instances had the issue, fresh install of 2.4.5 did not. But odd even a factory reset after upgrade and the issue remained in default config. I had to do full iso re-install to clear the problem.
-
@carl2187 said in Hyper-V VM constant 100% CPU Load in 2.4.5:
All my issues actually went away by doing clean install from ISO. Factory reset wasn't enough to eliminate the issue on 2.4.5 after upgrade. I clean installed 2.4.5 from iso, imported config, now i don't see any 100% spikes on my 4-core hyper-v gen2 zfs pfsense vms.
I wrote up all my findings on the issue here, I think its the same problem this thread is discussing:
https://forum.netgate.com/topic/149595/2-4-5-a-20200110-1421-and-earlier-high-cpu-usage-from-pfctl/25Although I see you mention a fresh install also has the issue in your case. In my situations only upgraded instances had the issue, fresh install of 2.4.5 did not. But odd even a factory reset after upgrade and the issue remained in default config. I had to do full iso re-install to clear the problem.
I bet its a BSD problem since the factory reset didnt do the job...
-
@carl2187
It's worth mentioning that my installation is using generation 1 of VMs. I'm gonna try installing using generation 2, though I could never get it to boot. -
@Cool_Corona I think the issue is in the upgrade logic, not 2.4.5 itself. a clean install from ISO has no issues at all. If there was an upstream BSD issue, new installs would suffer as well.
@UnknownEleven just make sure "Secure Boot" is disabled on the Gen2 vm to get the pfsense iso to boot.
-
I disabled secure boot in ESXi and still no dice....
-
@carl2187 Thanks for the tip. I'll try and let you know how it goes.
-
@Cool_Corona try Hyper-V or Linux KVM, I know pfsense works in those right now. I don't use vmware anywhere myself but you can attempt docs, looks like it should work fine, i used pfsense on it back in the esxi 5.x days: https://docs.netgate.com/pfsense/en/latest/virtualization/virtualizing-pfsense-with-vmware-vsphere-esxi.html
