On Tue, 29 Sep 2015 08:08:27 +0200 (CEST)
Alexandre DERUMIER wrote:
> >>Ok, but i guess that if we have several VMs into a Server, the problem be
> >>multiplied
> I'm not sure, because each vm have control of his own tcp congestion.
>
> (if it's bridged, the host
>>Ok, but i guess that if we have several VMs into a Server, the problem be
>>multiplied
I'm not sure, because each vm have control of his own tcp congestion.
(if it's bridged, the host shouldn't do nothing)
- Mail original -
De: "Cesar Peschiera"
À: "pve-devel"
@Alexandre DERUMIER:
I'm not sure, because each vm have control of his own tcp congestion.
(if it's bridged, the host shouldn't do nothing)
Ohh, ok, it isn't a great problem (i use KVM VM).
Many thanks for the clarification.
And please let me to do a question:
Is the same for conatiners (LCX
This is not a critical bug it merely affects network performance.
Ok, but i guess that if we have several VMs into a Server, the problem be
multiplied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
On Tue, 29 Sep 2015 01:24:36 -0400
"Cesar Peschiera" wrote:
>
> My Question:
> What will be the policy of PVE about of this?
>
This is not a critical bug it merely affects network performance.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael
The error affect almost all Linux distros
See the notice in this link:
http://bitsup.blogspot.com/2015/09/thanks-google-tcp-team-for-open-source.html
See the Google patch here:
https://github.com/torvalds/linux/commit/30927520dbae297182990bb21d08762bcc35ce1d
My Question:
What will be the