touch-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

** Tags added: kernel-da-key

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

Title:
  unable to start lxc on ubuntu

Status in linux package in Ubuntu:
  Incomplete
Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I've installed lxc on lubuntu utopic with a 3.18.3 lowlatency kernel,
  and I can't get lxc to start.  I'm getting the following errors in a
  logfile:

  lxc-start 1421773029.483 ERROR    lxc_conf - conf.c:instanciate_veth:2817 - failed to attach 'vethJCKW6M' to the bridge 'lxcbr0' : Operation not permitted
        lxc-start 1421773029.498 ERROR    lxc_conf - conf.c:lxc_create_network:3100 - failed to create netdev
        lxc-start 1421773029.498 ERROR    lxc_start - start.c:lxc_spawn:829 - failed to create the network
        lxc-start 1421773029.498 ERROR    lxc_start - start.c:__lxc_start:1087 - failed to spawn 'my32bitbox'
        lxc-start 1421773034.504 ERROR    lxc_start_ui - lxc_start.c:main:337 - The container failed to start.
        lxc-start 1421773034.504 ERROR    lxc_start_ui - lxc_start.c:main:339 - To get more details, run the container in foreground mode.
        lxc-start 1421773034.504 ERROR    lxc_start_ui - lxc_start.c:main:341 - Additional information can be obtained by setting the --logfile and --logpriority options.

  I tried looking at some of the other bugs where this was reported, but it seems to be different in my case to theirs.  Veth module is loading ok, and lxc-net service is started ok (according to initctl list).  I have tried purging and reinstalling.  I don't believe that I have bind9 running or installed.  I am using a custom compile with low latency enabled.
  uname -a = 3.18.3 #1 SMP PREEMPT Tue Jan 20 14:44:09 GMT 2015 x86_64 x86_64 x86_64 GNU/Linux

  I have threadirqs enabled in the grub commandline.  I am going to try
  with a generic low latency kernel.

  Thanks

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