[lxc-users] CRIU + lxc container

[Urgen Sherpa]

when i did reboot on container later fllowing error occured
root at ktmnp:/home/nplink/criu-1.1# lxc-info --name test-container
state:   RUNNING
pid:      9815
root at ktmnp:/home/nplink/criu-1.1# ./criu dump -D /dumps/ -o dumps.log -t
9815 --file-locks --tcp-established
root at ktmnp:/home/nplink/criu-1.1# cat /dumps/dump
dump.log   dumps.log
root at ktmnp:/home/nplink/criu-1.1# cat /dumps/dumps.log
Error (parasite-syscall.c:387): si_code=4 si_pid=10087 si_status=5
Error (parasite-syscall.c:387): si_code=4 si_pid=10091 si_status=5
Error (parasite-syscall.c:387): si_code=4 si_pid=10092 si_status=5
Error (tty.c:222): tty: Unexpected format on path /dev/lxc/tty4
Error (cr-dump.c:1493): Dump files (pid: 10172) failed with -1
Error (cr-dump.c:1828): Dumping FAILED.
root at ktmnp:/home/nplink/criu-1.1#


On Tue, Feb 4, 2014 at 11:54 AM, Urgen Sherpa <urgen.sherpa at nepallink.net>wrote:

> Hello,
> system used: ubuntu 13.1 X64bit RAM: 2G
> i was trying to check point lxc container(using CRIU which i compiled from
> source).
> steps follwed to check point were:-
> 1# lxc-create -n test-container -t ubuntu
> 2# lxc-start -n test-container       (//test-container is ubuntu12.04
> machine)
> 3)problem :=
> root at ktmnp:/home/nplink/criu-1.1# lxc-info -n test-container
> state:   RUNNING
> pid:      4643
> root at ktmnp:/home/nplink/criu-1.1# ./criu dump -t 4643 -D /dumps/ -o
> dump.log --tcp-established --file-locks
> root at ktmnp:/home/nplink/criu-1.1# cat /dumps/dump.log
> Error (sk-netlink.c:77): The socket has data to read
> Error (cr-dump.c:1493): Dump files (pid: 4832) failed with -1
> Error (cr-dump.c:1828): Dumping FAILED.
> root at ktmnp:/home/nplink/criu-1.1#
>
> any suggestions please
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20140204/53d67b88/attachment.html>