<div dir="ltr">Hi Pavel, and Serge<div><br></div><div>Thanks for the fast response. I understand the limitation. However, I would like to understand if criu can be used in its current version with lxc.</div><div>To allow for criu to work, I've tried the following combinations in lxc configuration files</div>
<div><br></div><div>lxc.console = none</div><div>lxc.tty = 0 </div><div><br></div><div>I am unable to start lxc using the stand lxc-start command. I am assuming this is because no consoles have been configured. I've tried starting the container as a daemon as well. That did not seem to work as well.</div>
<div><br></div><div>Thanks</div><div>Nipun</div><div><br></div><div>I am fairly new to lxc so I might be doing something wrong</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 4, 2013 at 1:48 PM, Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@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="im">On 12/04/2013 10:12 PM, Serge Hallyn wrote:<br>
> Quoting Nipun Arora (<a href="mailto:nipun@cs.columbia.edu">nipun@cs.columbia.edu</a>):<br>
>> Hi,<br>
>><br>
>> I've been tryint criu for checkpointing and restart. One of the issues is<br>
>> that criu does not support external console.<br>
>> I tried setting lxc.console = none, and lxc.tty = 0... but seem to get no<br>
>> progress when I run the following command..<br>
>><br>
>> lxc-create -t ubuntu -n test_lxc -f test_config<br>
>> lxc-start -n test_lxc<br>
>><br>
>> The config file basically has only the following 2 lines<br>
>> lxc.console = none<br>
>> lxc.tty = 0<br>
>><br>
>> Can someone help out in explaining why this is happening?<br>
><br>
> I think it's been explained before - the external console points<br>
> to a device file sitting in another mount namespace. criu can't<br>
> checkpoint that.<br>
<br>
</div>Ack.<br>
<div class="im"><br>
> Back in the in-kernel checkpoint days, IIRC we allowed such files<br>
> to be marked as uncheckpointable in the image, and the restart<br>
> program to fill those fds in with fds it had opened beforehand.<br>
><br>
> Can that be done with crui?<br>
<br>
</div>In theory -- yes. IOW -- we need to patch criu to achieve that. I<br>
planned to make this support using plugins to criu that help dumping<br>
external mount points. Currently Andrey works on such a plugin for<br>
external unix sockets, you can find his patches on the list From: avagin@.<br>
<br>
Similar thing can be done for external (bind)mounts. Does it make<br>
sense for you?<br>
<br>
> -serge<br>
<br>
Thanks,<br>
Pavel<br>
</blockquote></div><br></div>