touch-packages team mailing list archive

[James Page <james.page@xxxxxxxxxx>]

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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401658

Title:
  Host veth mtu not preserved during container reboot

Status in lxc package in Ubuntu:
  New

Bug description:
  LXC containers configured with lxc.network.mtu = 9000

  On start/restart using lxc-* commands, the mtu on the host and in
  container interface is correctly set to 9000.

  However, if the container is rebooted internally, the mtu of the veth
  on the host resets to 1500, whilst the container interface is still
  set to 9000.

  This causes some odd network behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1 [modified: usr/share/lxc/config/ubuntu.common.conf]
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Thu Dec 11 20:34:27 2014
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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