Hi folks,
I'm trying to figure out - why is there no documentation on the NEED to
configure MTU inside VM, when using vxlan as guest isolation method ?
Right now, by defaut/design, traffic/MTU goes like this:
eth0 inside VM is by default 1500 bytes -- vnetY mtu1450 -- virbrX
mtu1450-- vxlan
You should instead increase MTU on the host interface to accommodate. For
example, we used jumbo frames with an MTU of 9216 for the host interface. I
think it wasn't mentioned because its largely assumed in CS documentation
that the admin understands the network design they are using, i.e. you'd
Just want to clarify, with our 9216 MTU we easily run 9000 on our VMS. You
may want to set MTU to 1550 or greater on your KVM host interface used for
vxlan, and adjust the network accordingly. Most vxlan documentation for
network equipment should mention the 50 byte overhead and how to adjust for
Marcus, I understand that what you just said is possible and better
solution - but you should have to do this kind of changes on EVERY vxlan
interface/bridge, for every of your guest networks - so not a problem for
existing bridges - but a problem for new bridges that are going to be
deployed when
So here we go:
https://issues.apache.org/jira/browse/CLOUDSTACK-7790
I propose having ADMIN choose MTU size when deploying new Network/VPC
offer...that is per my understanding the only 100% working solution...
On 26 October 2014 16:57, Andrija Panic andrija.pa...@gmail.com wrote:
Marcus, I
