<div dir="ltr">AFAICT, dump is working. But not restore.<div><br></div><div>./test.py reports:</div><div><br></div><div>Success</div><div><br></div><div>But</div><div><div>criu restore -v2 -o restore-py.log -D imgs_py --shell-job || _exit $?</div>
<div> [just hangs]</div></div><div><br></div><div>imgs_py/restore_py.log says:</div><div><div>(00.000661) Error (include/util.h:51): Can't write img file: Operation not permitted</div></div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sun, Jan 5, 2014 at 3:03 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/05/2014 11:35 PM, Neal Becker wrote:<br>
> 1. The rpc_pb2.py is the same as the standard package as found here?<br>
><br>
> <a href="https://pypi.python.org/pypi/protobuf.socketrpc/1.3.2" target="_blank">https://pypi.python.org/pypi/protobuf.socketrpc/1.3.2</a><br>
<br>
</div>No. We have hand-made RPC based on messages from CRIU's protobuf/rpc.proto.<br>
</blockquote></div><br></div>