*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
The title of this bug is 'lxc stop will hang forever' - are you still
seeing that as well?
In both this and 1073238, you claimed that 3.7 fixed it for you. You're
saying that lvremove hanging happened in 3
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
I don't believe that this is a duplicate of Bug #1073238.
I'm able to replicate this relatively often on 3.5 and (I believe 3.8
from 13.04). lvremove remains unkillalble. I'm not using cgroups so I
don't t
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
I hope this helps someone some day:
>From what I observed: lvremove was failing to remove the COW device
because udev was occasionally doing a vgscan at the same time. This then
cause certain components to
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
I might try 3.7 later and see if I can get the memory cgroup working
again, but I'm not sure if I really need it.
3.6.3 is working with the memory cgroup disabled, I tested with over 400
iterations, I have
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
Quoting Tim (ice...@gmail.com):
> *** This bug is a duplicate of bug 1073238 ***
> https://bugs.launchpad.net/bugs/1073238
>
> :o the memory cgroup dissapeared when I switched to 3.6.3, is it also
> gon
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
:o the memory cgroup dissapeared when I switched to 3.6.3, is it also
gone in 3.7, is that why you asked me to comment out the memory setting?
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
I'll test that soon too :)
--
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/1071910
Title:
lxc
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
D'oh, I do believe I tested on a 3.7 kernel, so that would make sense :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://
Thanks for your suggestion Serge,
I believe I just solved the issue, except for the part I was seeing with
lvremove which appears to have some relation to:
udevd[7497]: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
vgchange -a y'' [11645]
udevd[7497]: 'watershed sh -c '/sbin/lvm
Can you confirm whether commenting out the line:
lxc.cgroup.memory.memsw.limit_in_bytes = 1024M
lets the container start?
--
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/1071910
Title
** Description changed:
Background:
This is issue occurs during an automated process and occurs with a 1/20
chance per iteration
I have one lxc-container on the machine
It is backed with an lvm2 snapshot
Running on ubuntu 12.10 on ec2 small instance - upgraded from 12.04 fresh
instance
typo in container config, actually using:
lxc.mount = /vms/vm1/fstab
instead of
lxc.mount = /vm1/vm1/fstab
--
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/1071910
Title:
lxc stop will ha
- Container config:
lxc.utsname = vm1
lxc.tty = 4
lxc.pts = 1024
lxc.rootfs = /vms/vm1/rootfs
lxc.mount = /vm1/vm1/fstab
lxc.network.type = veth
lxc.network.flags = up
lxc.network.name = eth0
lxc.network.link = br0
lxc.network.ipv4 = 192.168.3.2
# Set system resource limitations
lxc.cgroup.cpus
Could you please post the script which triggers this?
Note that you shouldn't need to manually mount and umount the lvm
partitions. If you've create the container with either 'lxc-create -t
ubuntu -B lvm -n q1' or 'lxc-clone -s -o q1 -n q2', then you can simply
'lxc-start -n q1' (or q2) to start
14 matches
Mail list logo
