That's not what I meant either. I was just answering initially about the theoretical concern, mostly following @planedrop logical question, in other words "before fearing something, test it for real and see the real impact toward your requirements".
We already know you are affected, it's like you were afraid we wouldn't care about your use case while we are already deeply invested into getting a solution to a tricky problem that could affect some people in some situations.
Yes but I don't think there's a need to add another "layer on the cake" about this, you already know we are convinced already about getting it fixed in priority and investing nearly half a million already to fix it.
It's really rare when it could become a blocker, and the proof is it took years to people to even notice (even us, having an EPYC production infrastructure).
I wasn't addressing you but @linuxmoose having theoretical concerns.
@linuxmoose said in Epyc VM to VM networking slow:
I feel that this is going to be a much larger issue for us.
Before that I would strongly encourage to test if it's really a problem, because it's really not in 90% of the use cases we've seen.
Thanks for your report @BSmithITGuy
Let me ping @lsouai-vates about this so we can find a way to do better 
This message shouldn't appear if the license is properly activated. Since you have an active XOA trial, you should open an official ticket through the support portal and we can take a look at this for you.
Still, I remember we had a dedicated CLI tool to test it 
