Please open a new bug for your issue, using 'ubuntu-bug lxc' (though
actually I am suspecting a dnsmasq bug). It may be the same issue as
this bug, but many variables are different.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On an 800 Mhz machine I can quite consistently reproduce startup
failures and conflicting IPs with ext3 instead of btrfs with only two
containers.
Additional Information:
A brand new install of Ubuntu 13.04 Server AMD64 with all updates applied.
$ sudo lxc-ls --fancy
NAME STATEIPV4
You mention you tested v3.11-rc2 in comment #5. Can you also test the latest
mainline kernel, which is v3.11-rc6:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc6-saucy/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So it sounds like the bug still exists in the latest Mainline kernel,
and it has been around since at lease the 3.2 kernel. Do you happen to
know if there was a previous release that did not exhibit this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I only started using lxc+btrfs in the past few months, so unfortunately
I have no information about the behavior of any previous kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214085
Title:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Brad Figg: I'm happy to do this, but this is a server without a GUI, and
the spawned w3m instance is unable to properly display the login form
page.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Joseph Salisbury: I installed v3.11 RC2 and successfully reproduced the
problem using the same technique. The result remains the same - after a
series of simultaneous clone/start operations, LXC eventually fails to
be able to start any additional containers.
** Changed in: linux (Ubuntu)
Additional note: I've found the problem manifests more easily with the
following modified test script (this one forks all LXC clone/start
operations immediately):
test.sh:
#!/usr/bin/env bash
prefix=$1
test -z ${prefix} echo 'error: missing required parameter: prefix'
12
