On Thu, 8 Dec 2011, Arie Skliarouk wrote:
> When I tried to restart the vserver, it did not came up. Long story short,
> I found that lxc-destroy did not destroy the cgroup of the same name as the
> server. The cgroup remains visible in the /sys/fs/cgroup/cpu/master
> directory. The tasks file is empty though.
And just now, I've had the same thing happen - a container failed to
start and it left it's body in /cgroup - with empy tasks.
This is latest & greatest - kernel 3.1.4, lxc 0.7.5, Debian squeeze
(kernel & lxc compiled)
It may well have been my own fault - trying to start a container whos
disk image was NFS mounted and I got the error:
mount.nfs: an incorrect mount option was specified
and lxc-start hung. so I may be doing something bogus anyway, however...
(like e.g. trying to bind-mount /proc, /sys, /dev/pts, etc. into an nfs
mounted directory?)
Gordon
------------------------------------------------------------------------------
Learn Windows Azure Live! Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for
developers. It will provide a great way to learn Windows Azure and what it
provides. You can attend the event by watching it streamed LIVE online.
Learn more at http://p.sf.net/sfu/ms-windowsazure
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
