Maxed RAM and Hanging with Hyper-V 2019
-
Hello! I have pfSense running in a VM. It started as pfSense 2.4.4p3 on a Hyper-V 2016 VM where is worked perfectly but recently the host was upgraded to Hyper-V 2019. Since then, I have been having a variety of problems. The problems started with my IPsec tunnels not passing traffic (was getting bytes in but not out). I saw IPsec bugfixes in 2.4.5 so I updated. When I updated, my IPsec tunnels didn't work but now pfSense maxes out any amount of RAM I give it. Does anyone have any ideas?
-
Well, based on your description of the timeline and subsequent events, I would suspect an issue exists with FreeBSD 11-STABLE as a guest OS and Hyper-V 2019. That would be something to perhaps ask upstream at the FreeBSD level or maybe over on the Microsoft side (but to be honest, I wouldn't expect much help from the Microsoft side).
pfSense-2.4.4_p3 was based on FreeBSD 11.2. The latest pfSense-2.4.5 is based on FreeBSD-STABLE (which is, I think, in reality 11.3).
-
My problem has solved by selecting the pfsense 2.4.5 virtual machine as generation 1 instead of generation 2. I think FreeBSD 11.3 has some sort of problem with the Hyper-V.
-
https://azuremarketplace.microsoft.com/en-us/marketplace/apps/microsoftostc.freebsd-11-3?tab=PlansAndPrice
Not that this means much, but I would think if MS is marketing FreeBSD 11.3 on Azure, they've worked out the bugs. This is all I could find though. Making several assumptions.
-
I have been using a gen 1 VM so unfortunately that doesn't resolve the issue.
