I've added DECLARE_ARG("--evasive-devices"); in lxccontainer.c/exec_criu and I
was finally able to dump the container. It also restored but only when both -V
and -d were passed to lxc-checkpoint.
But lxc-stop, lxc-attach, etc. hang after the container is restored. But that
is expected at this point, isn't it?
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");
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) ========================================
Krystof
_______________________________________________
lxc-devel mailing list
lxc-devel@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-devel
