<div dir="ltr">It looks like a permission issue. If run as root:<div><div>sudo criu restore -v4 -o restore-py.log -D imgs_py --shell-job || _exit $?</div><div>[sudo] password for nbecker: </div><div>Success</div><div>Restored</div>
</div><div><br></div><div>But the whole idea of using the daemon was that we don't need root to dump/restore, correct?</div><div><br></div><div>The restore_py.log I showed WAS the whole file.</div><div><br></div></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jan 5, 2014 at 3:22 PM, Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 01/06/2014 12:17 AM, Neal Becker wrote:<br>
> AFAICT, dump is working. But not restore.<br>
><br>
> ./test.py reports:<br>
><br>
> Success<br>
><br>
> But<br>
> criu restore -v2 -o restore-py.log -D imgs_py --shell-job || _exit $?<br>
<br>
</div>The -v4 is much more verbose.<br>
<br>
> [just hangs]<br>
<br>
It hangs waiting for restore task to exit. You can check with ps -axf what<br>
processes appeared and in which state. The -d (--restore-detached) option<br>
can help to handle this.<br>
<div class="im"><br>
> imgs_py/restore_py.log says:<br>
> (00.000661) Error (include/util.h:51): Can't write img file: Operation not permitted<br>
<br>
</div>Can you show the full restore-py.log file? On restore the only file written<br>
should be the restore stats one.<br>
<br>
Thanks,<br>
Pavel<br>
</blockquote></div><br></div>