[CRIU] [lxc-devel] [PATCH] Add support for checkpoint and restore via CRIU

[Tycho Andersen]

On Tue, Sep 16, 2014 at 11:11:04PM +0000, Zmudzinski, Krystof C wrote:
> I've added DECLARE_ARG("--evasive-devices"); in lxccontainer.c/exec_criu and I was finally able to dump the container.

Ok, I've been trying to produce a situation where this is necessary
but I couldn't. Can you paste your lxc configuration file?

> It also restored but only when both -V and -d were passed to lxc-checkpoint.

-V isn't an argument to lxc-checkpoint. (Perhaps you mean -v? That
/shouldn't/ affect things, it is just logging.) What happens when you
don't pass -d?

> But lxc-stop, lxc-attach, etc. hang  after the container is restored.  But that is expected at this point, isn't it?

No, those should work. Can you show the output of ps auxf?

> The interesting part is that something like this is not needed but it is used in run.sh
> 
> DECLARE_ARG("-n net -n mnt -n ipc -n pid");

That's not needed, it is an old criu option (CRIU's wiki is outdated).

> Lastly, could criu dump the entire command line to the logs when it is executed?  So the beginning of the log starts with something like:
> 
> (00.000047) ========================================
> (00.000057) /usr/local/sbin/criu dump --tcp-established --evasive-devices --file-locks --link-remap --manage-cgroups.......
> (00.000087) Dumping processes (pid: 22614)
> (00.000093) ========================================

The log itself is generated by criu, so that is probably a question
for the criu list, not the lxc list :)

Tycho

> Krystof
> 

> _______________________________________________
> lxc-devel mailing list
> lxc-devel at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-devel