[CRIU] dedup and memory tracking
Pavel Emelyanov
xemul at parallels.com
Wed Jun 11 06:12:57 PDT 2014
On 06/11/2014 05:07 PM, J F wrote:
> Provided you use the --track-mem and --prev-images options, the behavior is
> not expected to be like this. BTW, there was a bug on the 'Incremental dump'
> page -- the --track-mem option should be used always
>
>
> Yes, I'm doing
>
> sudo ./criu-main-branch/criu/crtools dump --tree $pid --tcp-established --shell-
> job --images-dir /mnt/mydata/$dumpdir --leave-running --track-mem
>
> followed by 2nd dump:
>
> sudo ./criu-main-branch/criu/crtools dump --tree $pid --tcp-established --shell-
> job --prev-images-dir /mnt/mydata/$prevdumpdir --images-dir /mnt/mydata/$newdump
> dir --leave-running --track-mem --auto-dedup
Is $prevdumpdir == $dumpdir ?
> Do you have memory tracker compiled in the kenrel? The "criu check" option
> can check this, what does it tell?
>
>
> /mnt/mydata/criu-main-branch/criu$ sudo ./crtools check
> Looks good.
>
More information about the CRIU
mailing list