[Bug 1401658] Re: Host veth mtu not preserved during container reboot

James Page james.page at ubuntu.com
Fri Dec 12 08:58:54 UTC 2014


I think I see what the problem is; the containers on these hosts where
created with mtu 1500; i then updated the configuration files to set the
mtu to 9000 + set the veth mtu's to 9000 using:

   ip link set vethXXXX mtu 9000

This means that the container was started using an mtu of 1500 not 9000.

Rebooting the container internally results in the host mtu re-setting to
1500.

This is a general side effect of trying to massage mtu's to 9000 to
support jumbo frames in openstack deployments.

** Changed in: lxc (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401658

Title:
  Host veth mtu not preserved during container reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1401658/+subscriptions



More information about the Ubuntu-server-bugs mailing list