[CRIU] Problem with CRIU

Cyrill Gorcunov gorcunov at gmail.com
Mon Apr 28 05:04:41 PDT 2014


On Mon, Apr 28, 2014 at 02:53:23PM +0530, Krishan Berwal wrote:
>    Dear sir/mam,
> 
>    i am showing what is actual output after follow the procedure:
> 
>    root at 3451eead64b2:~/kk#A  setsid ./abc.shA  < /dev/null &> abc.log &
>    [2] 119
>    root at 3451eead64b2:~/kk# ps -C abc.sh
>    A  PID TTYA A A A A A A A A  TIME CMD
>    A A  42 pts/0A A A  00:00:00 abc.sh
>    [2]-A  DoneA A A A A A A A A A A A A A A A A A A  setsid ./abc.sh <
>    /dev/null &>abc.log
>    root at 3451eead64b2:~/kk# criu dump -vvvv -o dump.log -t 42 --shell-job &&
>    echo OK
>    root at 3451eead64b2:~/kk#A  criu restore -vvvv -o restore.log -t 42
>    --shell-job
>    root at 3451eead64b2:~/kk# ls
>    abc.logA  abc.shA  dump.logA  restore.log
>    root at 3451eead64b2:~/kk# cat dump.log
>    (00.000090) ========================================
>    (00.000150) Dumping processes (pid: 42)
>    (00.000157) ========================================
>    (00.000312) Error (kerndat.c:45): Can't stat self map_files: Operation not
>    permitted

If you're running under root user and get EPERM, it looks like you've some
kind of additional layer of restriction, maybe selinux/apparmor or someone
else is blocking criu from execution.


More information about the CRIU mailing list