[Bug 1100877] Re: lxc-start fails after upgrade to raring

[Stéphane Graber]

FWIW, the original error message is usually caused by one of:
 - Server using ksplice which breaks the veth driver, requires a reboot
 - Machine with kernel module version mismatch causing the veth driver to fail to load
 - Machine with a kernel lacking veth support or missing the .ko or depmod entry


In all of those cases, there isn't much LXC can do and the following should fail just as much "sudo ip link add dev veth".

-- 
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/1100877

Title:
  lxc-start fails after upgrade to raring

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