[solved] pfSense (2.6.0 & 22.01 ) is very slow on Hyper-V
-
@emigu you blame whoever you want to blame.. If it makes you feel better..
-
@emigu Next time check the beta and file a bug report if you depend upon running it on hyper-v I guess.
But I am not sure if that would stop them to release a new final, I really have no clue. -
@bob-dig said in pfSense (2.6.0 & 22.01 ) is very slow on Hyper-V:
@emigu said in pfSense (2.6.0 & 22.01 ) is very slow on Hyper-V:
Clearly there were 0.0% tests done with Hyper-V (One of the largest hypervisors in the world).
I am with you on that but Netgate doesn't make money with hyper-V. And Azure has no similarities with anything MS is selling for bare metal installations. So in the end you can be happy if it is running on your own "hardware" anyways, they don't have to support it.
And I think that hyper-V probably will be let down even from MS like everything else that is not running in their cloud. Let's see.What are you on about?
Azure runs on Hyper-V.
They've ran a modified version of Hyper-V (Obviously, same as AWS runs on an inhouse modified version of KVW, and previous XEN) - GCP has their complete own Hypervisor, Borg I believe it's called.
These days MS has released said modified Hyper-V: Azure Stack HCI.
They're obviously going to stop developing Hyper-V in the future, and leave it as is right now as a very lightweight hypervisor - which is why they're making HCI trial free for customers whom want to run their own HW with the same hypervisor Azure does for Azure integration.
-
@emigu Azure was tested if I remember correctly and didn't had that problem they said.
-
@bob-dig said in pfSense (2.6.0 & 22.01 ) is very slow on Hyper-V:
@emigu Next time check the beta and file a bug report if you depend upon running it on hyper-v I guess.
But I am not sure if that would stop them to release a new final, I really have no clue.No, I won't. My intention was to pay for pfSense and thus expect compability and testing to be done by the developers (Which is a big reason why you pay for software) but if such a basic test as automating a pfsense setup on each hypervisor, creating a random VM and running speedtest-cli isn't done - I wouldn't trust that product in production even when it's free.
My time is valuable and I do not intend on spending it doing basic testing for a company too lazy or incompetent (In the case def. the former) to QA their software. I prefer paying for that service and keeping my time to business values.
-
Azure was unaffected because it doesn't support the RSC vswitches that caused the problem as I understand it. Hence none of the testing we did there revealed this issue.
Steve
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
W werter referenced this topic on
-
@stephenw10 I can confirm just like @hendryjl that this happens VM to VM in the same host or across Hyper-V hosts. Disabling RSC in the vSwitch fixed the issue I was having with pfSense 2.6.0. I didn't want to update to 2.7_devel branch, and didn't want to go back to 2.5.2. Will wait for 2.7 CE to be officially released and test again.
