Quoting Christoph Mathys (erase...@gmail.com):
I've been digging further and also tested with Ubuntu mainline
kernels. To detect if the problem has been triggered I resorted to
'script' which fails to allocate a pty in the error case. For the
problem to occur, lxc.autodev = 1 seems to be
Hi,
I am using lxc-1.0.7 and while lxc-start I am getting this error
lxc/start.c: __lxc_start: 1080 failed to spawn 'vm0
lxc/cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir:
failed to delete /cgroup/lxc/vm0
My mount output is :
/dev/sda10 on / type ext4
Quoting Divya Vyas (edivya.v...@gmail.com):
Hi,
I am using lxc-1.0.7 and while lxc-start I am getting this error
lxc/start.c: __lxc_start: 1080 failed to spawn 'vm0
lxc/cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir:
failed to delete /cgroup/lxc/vm0
My mount output
Hi everyone,
I was wondering if someone could help me out defining all the required
kernel configuration option in order to seamlessly use LXC.
I used the lxc-checkconfig to test the basic configuration but, I am still
not able to get any ip address assigned to the container.
Hi,
I am using lxc-1.0.7 and while lxc-start I am getting this error
lxc/start.c: __lxc_start: 1080 failed to spawn 'vm0
lxc/cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir:
failed to delete /cgroup/lxc/vm0
My mount output is :
/dev/sda10 on / type ext4
Hello,
sometimes I've got many bridge created by lxc containers that are kept
up even after bringing down the container (case happens when I update
all containers with python API, and container fails to bring down
properly).
Moreover, I've set a bridge interface quota in /etc/lxc/lxc-usernet
which
