In general if no MTU is set on interface creation the default value is 1500.
On OVS the bridge MTU is automatically set to the smallest port MTU. So
you just have to set the MTU of each port of the bridge.
Take a look at: https://bugzilla.redhat.com/show_bug.cgi?id=1160897
It is a bit of a pain to read but seems to confirm the statement about
the OVS MTU value being set by the MTU of the ports.
I have been using OVS with Xen and a few years ago I had to wrap my head
around this problem.
Once you start setting the MTU to something other than 1500 you will
find you need to set ALL the MTU values of ALL your interfaces.
Otherwise some inherited default will bite you.
On 7/31/19 4:39 AM, Michal Privoznik wrote:
On 7/29/19 9:23 PM, Sven Vogel wrote:
Hi Michal,
Thanks for your answer.
I don’t understand why an interface created without mtu gets only
1500 visible in the virtual machine but if I create an interface with
mtu higher than 1500 e.g. 2000 the bridge will change too. Before the
bridge was e.g. by 9000.
I ask because you wrote if I don’t set an mtu of the interface I will
get the mtu of the bridge. But it seems so.
Can you clarify it a little better for me?
I don't know enough about OVS internals to answer that, sorry. Maybe
we should ask OVS developers why OVS bridge behaves this way.
Michal
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users
--
Alvin Starr || land: (647)478-6285
Netvel Inc. || Cell: (416)806-0133
alvin@xxxxxxxxxx ||
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users
