Public bug reported:
If there are 20-30 containers, not all get started.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lxc 0.7.5-3ubuntu65
ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
Uname: Linux 3.2.0-34-generic x86_64
ApportVersion: 2.0.1-0ubuntu15
Architecture: amd64
Date:
create command: lxc-create -n CONTAINER -t ubuntu
containers are under the directory /data/lxc (mv /var/lib/lxc/CONTAINER
/data/lxc)
/etc/lxc/lxc.conf:
lxc.network.type=veth
lxc.network.link=br-eth0
lxc.network.flags=up
/etc/default/lxc:
LXC_AUTO="true"
USE_LXC_BRIDGE="false"
LXC_BRIDGE="lxcb
I need to find a proper ide time to be able to reboot the server.
I hope, I can do it soon.
--
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/1087765
Title:
Not all containers get started
After the last reboot all containers started as expected, thus I could
not reproduce this issue.
** Changed in: lxc (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bu
Public bug reported:
The problem described in #277120, but it's closed with INVALID.
So again, the option --pidfile is not used in the init script, because it's
value gets overwritten by sshd_config settings.
It should get the right value from the config file, which is defined in
/etc/default/s
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/801123
Title:
sshd init script does not use the option "--pidfile"
To manage notifications about this bug go to:
https://bugs.launchpa
Public bug reported:
# lxc-ls
jay log0 pict
jay log0 log0 pict
Before this I updated a Precise container. While update was running, mysql
server could not be stopped. I rebooted the container inside from it with
'reboot'.
After lxc-stop & start everything looks fine except mysql. It can
--
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/974172
Title:
lxc-ls show duplicated names
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bu
** Attachment added: "strace dump of lxc-ls"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/974172/+attachment/3008781/+files/lxc-ls.zip
--
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/b
Public bug reported:
There is a post with very similar symptoms on serverfault:
http://serverfault.com/questions/609881/windows-server-2012-on-kvm-on-
ubuntu-14-04-runs-well-for-a-while-and-then-slows/612084#612084
Basically all kind of KVM guests are getting slow by time, both windows or
linu
On 07/14/2014 05:13 PM, Serge Hallyn wrote:
> Since "switching to saucy kernel is a good workaround", marking this as
> affecting the kernel.
>
> Could you try disabling KSM and see if that avoids the issue?
I set KSM_ENABLED=0 in /etc/default/qemu-kvm and restarted the server.
Also today after 3
On 07/16/2014 06:35 PM, Serge Hallyn wrote:
> To be clear, you have not yet gotten the bug since you've set
> KSM_ENABLED to 0, or have you?
I just did it, so no, not yet.
This happened by time:
Saucy (everything is fine) -> Trusty (issue happened) -> Trusty with
Saucy kernel 3 weeks ago (no
On 07/16/2014 09:39 PM, Serge Hallyn wrote
> I've personally not seen it, and noone on my team, who use a lot of
> kvm instances, has seen it. Our two current theories are that (a) it
> has to do with ksm page migration across numa-nodes, or (b) it has to
> do with a race with transparent hugepage
On 07/16/2014 10:24 PM, Serge Hallyn wrote:
> (To be sure - /sys/kernel/mm/ksm/run is in fact set to 0 now right?)
Right.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1341195
Title:
FYI, I see no issue since I set KSM_ENABLED=0 (1 day).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1341195
Title:
KVM guests getting slow by time
To manage notifications about this
I think we can be sure, that KSM_ENABLED=0 definitely helps.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1341195
Title:
KVM guests getting slow by time
To manage notifications abou
It's true. Thank you.
--
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/753308
Title:
Restart containers on upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Sorry right now I don't use a clean natty nor maverick install.
I downgraded to 0.7.4-0ubuntu7.1, than apt-get upgrade:
$ apt-get install lxc
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are
18 matches
Mail list logo
