[CRIU] ubuntu container dump error

[riya khanna]

I modified the "--root" option, but the command below fails:

$ criu restore --evasive-devices --tcp-established --file-locks -n net
-n mnt -n ipc -n <pid> --action-script "`pwd`/network-script.sh
restore $name.0" --veth-pair eth0=$name.0 --pidfile newpid.log --root
/usr/local/lib/lxc/rootfs -vvvv -D data -d -o restore.log

(00.013816)      1: Path `/usr/local/lib/lxc/rootfs' resolved to `./' mountpoint
(00.013823)      1: Error (mount.c:1777): New root and old root are the same
(00.082318) Error (cr-restore.c:1050): 16733 exited, status=1
(00.082365) Error (cr-restore.c:1613): Restoring FAILED.

Also, if I remove the "--root" option then, it fails with the following error:

(00.470598)      1: cg: Move into 2
(00.470605)      1: cg:   `-> blkio//lxc/test/tasks
(00.470618)      1: Error (cgroup.c:275): cg: Can't move into
blkio//lxc/test/tasks (-1/-1) : No such file or directory
(00.487982) Error (cr-restore.c:1050): 15792 exited, status=255
(00.488012) Error (cr-restore.c:1613): Restoring FAILED.

The log is attached.

On Fri, Jun 6, 2014 at 4:32 AM, Pavel Emelyanov <xemul at parallels.com> wrote:
> On 06/06/2014 12:29 PM, riya khanna wrote:
>> Yes, that does the trick. Thanks! I thought I'd tried that. Never mind.
>>
>> However, restore fails:
>>
>> (00.015354)      1: Error (mount.c:1755): chdir(/root/test-lxc-root)
>> failed: No such file or directory
>> (00.076583) Error (cr-restore.c:1050): 32397 exited, status=1
>> (00.076632) Error (cr-restore.c:1613): Restoring FAILED.
>>
>
> Probably you've missed the --root option for restore. It shows where
> the container's root should be, and this path should be a mount point.
>
>
> Thanks,
> Pavel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: restore.log
Type: application/octet-stream
Size: 266933 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140608/86343243/attachment-0001.obj>