12: virbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 52:54:00:50:bc:b9 brd ff:ff:ff:ff:ff:ff
13: vnet4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master virbr2 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether fe:54:00:9e:dd:ca brd ff:ff:ff:ff:ff:ff
AFAIK this is stock kernel quirk behaviour; an empty bridge will be mtu 1500 no matter what you toss at it.
Until you add an interface to it, then it assumes the MTU of that interface.
Linux distribution
Fedora 34 x86_64
Description of Issue/Question
Setting an MTU on a network and subsequently adding VM's to it leads to both the bridge and VM interface MTU still set to 1500.
Setup
Steps to Reproduce Issue
On any libvirt with or without the terraform driver, create (just) a network.
The above tf code created an mtu=6789 bridge,
virsh net-dumpxml chmtu
:And a VM intf there
virsh dumpxml mtuvm
:-BUT-
ip -l
:AFAIK this is stock kernel quirk behaviour; an empty bridge will be mtu 1500 no matter what you toss at it. Until you add an interface to it, then it assumes the MTU of that interface.
XSLT workaround fix:
Results
virsh dumpxml mtuvm
ip l