touch-packages team mailing list archive

[Serge Hallyn <1373981@xxxxxxxxxxxxxxxxxx>]

Thanks for submitting this bug.

To be clear,

'sudo ip link add type veth'

also returns an error?

Could you tell us which ami and which machine type you used to start the
amazon instance?

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

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

Title:
  ubuntu 14.10 server, amd64 - lxc-start fails to start container

Status in “lxc” package in Ubuntu:
  Incomplete

Bug description:
  I had previously created an lxc container successfully using either:
  $ sudo lxc-create -t download -n test_cn
  -or-
  $ sudo lxc-create -t ubuntu -n test_cn

  However... when trying to start it fails with the following?
   
  $ sudo lxc-start -n test_cn
  lxc-start: failed to create vethBQ6TPB-vethV9VF9A : Operation not supported
  lxc-start: failed to create netdev
  lxc-start: failed to create the network
  lxc-start: failed to spawn 'test_cn'
  lxc-start: The container failed to start.
  lxc-start: Additional information can be obtained by setting the --logfile and --log-priority options.

  To check if the "veth" kernel module is loaded I updated the server
  and rebooted

  I ran "sudo modprobe veth" and it shows an error also?

  $ sudo modprobe veth
  modprobe: ERROR: could not insert 'veth': Cannot allocate memory

  
  This server is running on AWS EC2.

  $ uname -a
  Linux ip-10-69-148-9 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

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