[Lxc-users] Can't start containers

[Milan Zamazal]

>>>>> "SH" == Serge Hallyn <serge.hallyn at canonical.com> writes:

    SH> Does /proc/self/mounts on the host change after you successfully
    SH> start the container the first time?

I examined /proc/self/mounts at the beginning and at the end of
/etc/init.d/lxc script.  The only difference is:

  < cgroup /cgroup cgroup rw,relatime,perf_event,blkio,net_cls,freezer,devices,cpuacct,cpu,cpuset 0 0
  ---
  > cgroup /cgroup cgroup rw,relatime,perf_event,blkio,net_cls,freezer,devices,cpuacct,cpu,cpuset,clone_children 0 0

Nothing gets changed in /proc/self/mounts thereafter.
    
    SH> Can you do 'lxc-start -n test -l DEBUG -o test.debug', twice,
    SH> and send us the resulting test.debug file?

The two debug outputs are attached.  There is no significant difference
in the outputs until the pivot_root call.  Please note that I commented
out the lxc.rootfs.mount option so the mounts happen at default location
rather than in /mnt/lxc reported in my previous message.  My Linux
version is 3.2.0 from Debian testing.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.debug.on-boot
Type: application/octet-stream
Size: 10465 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20120331/1b0dfb4d/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.debug.later
Type: application/octet-stream
Size: 7533 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20120331/1b0dfb4d/attachment-0001.obj>