[CRIU] system configuration for dumping/restoring LXC
Andrew Vagin
avagin at parallels.com
Thu Sep 11 13:31:59 PDT 2014
On Thu, Sep 11, 2014 at 10:50:45AM -0700, Krystof Zmudzinski wrote:
> 22. This time I got: bridge br0 does not exist!
> 23. I edited network-script.sh accordingly
> 24. Dump doesn't work. See attached dump1.log.
> 25. So I went back to the way I originally created the container. I changed
> rootfs in test-lxc.conf to /root/test-lxc
> 26. I created the container and started it and I was able to dump it; see
> attached dump2.log
> 27 However, the restore hangs. ps a shows these processes but there is no
> init; see attached restore.log
Welcome to the club:
http://lists.openvz.org/pipermail/criu/2014-September/016190.html
I will write tomorrow, what we will need for investigating this problem.
Tycho, could you read the previous email from Krystof? I think you have
more experience of dumping LXC containers.
Thanks,
Andrew
>
> 413 pts/1 S+ 0:00 /bin/bash ./run.sh test-lxc
> 498 pts/1 S+ 0:00 /root/criu-1.3/criu restore --evasive-devices
> --tcp-e
> 499 pts/1 t+ 0:00 /root/criu-1.3/criu restore --evasive-devices
> --tcp-e
>
More information about the CRIU
mailing list