<div dir="ltr">Hi Andrew and Pavel,<div><br></div><div>I've tried setting both lxc.tty=0, and lxc.console=none. </div><div>I end up being unable to start the lxc container itself. </div><div><br></div><div>Just as a background for my testing environment. </div>
<div>I am using a ubuntu virtualbox launched using vagrant (I don't think this should make any difference as it's essentially running ubuntu 12.04 in a VM)</div><div><br></div><div>The linux container is an ubuntu 12.04 precise container. </div>
<div><br></div><div>I've tried starting the container using the following configuration</div><div><br></div><div>cat lxc.conf</div><div>>></div><div>lxc.tty=0</div><div>lxc.console=none</div><div>>></div>
<div>
<br></div><div>trying to start lxc both as a daemon or otherwise does not seem to work..</div><div><br></div><div>lxc-start -n lxc_test1 -t ubuntu -f lxc.conf</div><div><br></div><div>or with the -d option for daemon. </div>
<div><br></div><div>I tried ssh'ing into the container to see if the lxc-start was successful but that did not work either.</div><div>Could you tell me what I need to modify?</div><div><br></div><div>Thanks</div><div>
Nipun</div><div> </div><div>P.S - I guess you guys are in both lists - lxc, and criu so I'm sorry about the spam :)</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Dec 1, 2013 at 12:21 PM, Andrew Vagin <span dir="ltr"><<a href="mailto:avagin@parallels.com" target="_blank">avagin@parallels.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Sun, Dec 01, 2013 at 08:36:32AM +0400, Pavel Emelyanov wrote:<br>
> On 11/29/2013 11:39 PM, Nipun Arora wrote:<br>
> > Hi all,<br>
> ><br>
> > Thanks for the assist, I still seem to be having problems. Is there any other specific configuration flags I need to be aware of ?<br>
> > Even with the lxc.console = none in the config still seem to have some issues.<br>
><br>
> Below is the list of mounts found in you container's mount namespace:<br>
><br>
> (00.153292) [/](68->40)<br>
> (00.153295) [/run](44->68)<br>
> (00.153298) [/run/user](47->44)<br>
> (00.153301) <--<br>
> (00.153303) [/run/lock](45->44)<br>
> (00.153306) <--<br>
> (00.153308) [/run/shm](46->44)<br>
> (00.153311) <--<br>
> (00.153313) <--<br>
> (00.153315) [/proc](69->68)<br>
> (00.153318) <--<br>
> (00.153320) [/sys](70->68)<br>
> (00.153323) [/sys/fs/cgroup](43->70)<br>
> (00.153325) <--<br>
> (00.153328) [/sys/fs/fuse/connections](71->70)<br>
> (00.153330) <--<br>
> (00.153333) [/sys/kernel/debug](72->70)<br>
> (00.153335) <--<br>
> (00.153338) [/sys/kernel/security](73->70)<br>
> (00.153340) <--<br>
> (00.153342) [/sys/fs/pstore](74->70)<br>
> (00.153345) <--<br>
> (00.153347) <--<br>
> (00.153350) [/dev/lxc/tty1](75->68)<br>
> (00.153352) <--<br>
> (00.153355) [/dev/lxc/tty2](76->68)<br>
> (00.153357) <--<br>
> (00.153359) [/dev/lxc/tty3](77->68)<br>
> (00.153362) <--<br>
> (00.153364) [/dev/lxc/tty4](78->68)<br>
> (00.153367) <--<br>
> (00.153369) [/dev/pts](41->68)<br>
> (00.153372) <--<br>
> (00.153374) [/dev/ptmx](42->68)<br>
> (00.153377) <--<br>
> (00.153379) <--<br>
> (00.153387) Error (mount.c:254): 78:/dev/lxc/tty4 doesn't have a proper root mount<br>
> (00.153819) Error (namespaces.c:442): Namespaces dumping finished with error 65280<br>
><br>
> The Error mount.c:254 says, that you still have bind mounted tty-s<br>
> in your container and the list of mounts says you do. Maybe there's<br>
> some other stuff in the container's config file you should tweak?<br>
<br>
</div></div>lxc.tty=0<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Optionally you can unmount the /dev/lxc/tty* by hands before running criu dump.<br>
><br>
> > Here is the dump.log attached...<br>
> ><br>
> > Thanks<br>
> > Nipun<br>
><br>
> Thanks,<br>
> Pavel<br>
</div></div></blockquote></div><br></div>