On 2017-03-31 4:28 PM, Ian Pilcher wrote:

BZ here - https://bugzilla.redhat.com/show_bug.cgi?id=1438069

Wondering, though, if this is expected behavior, and I need to do something specific to enable larger frames on an OVS bridge with kernel 4.10.

Nope, that's a bug. Someone reworked the upstream MTU handling code, and missed a few places that needed updates (hint: it was me). They've been fixed in net-next, and I *thought* were cc'd to -stable, but they don't seem to be there just yet... These are the relevant upstream commits:

commit 3331aa378e9bcbd0d16de9034b0c20f4050e26b4 Author: Jarod Wilson jarod@redhat.com Date: Mon Mar 6 08:48:58 2017 -0500

team: use ETH_MAX_MTU as max mtu

commit 31c05415f5b471fd333fe42629788364faea8e0d Author: WANG Cong xiyou.wangcong@gmail.com Date: Thu Mar 2 12:24:36 2017 -0800

bonding: use ETH_MAX_MTU as max mtu

commit 425df17ce3a26d98f76e2b6b0af2acf4aeb0b026 Author: Jarno Rajahalme jarno@ovn.org Date: Tue Feb 14 21:16:28 2017 -0800

openvswitch: Set internal device max mtu to ETH_MAX_MTU.