[CRIU] criu-1.1-rc1 segfaults on fedora 20 x86_64

[Neal Becker]

It looks like a permission issue.  If run as root:
sudo criu restore -v4 -o restore-py.log -D imgs_py --shell-job || _exit $?
[sudo] password for nbecker:
Success
Restored

But the whole idea of using the daemon was that we don't need root to
dump/restore, correct?

The restore_py.log I showed WAS the whole file.



On Sun, Jan 5, 2014 at 3:22 PM, Pavel Emelyanov <xemul at parallels.com> wrote:

> On 01/06/2014 12:17 AM, Neal Becker wrote:
> > AFAICT, dump is working.  But not restore.
> >
> > ./test.py reports:
> >
> > Success
> >
> > But
> > criu restore -v2 -o restore-py.log -D imgs_py --shell-job || _exit $?
>
> The -v4 is much more verbose.
>
> >  [just hangs]
>
> It hangs waiting for restore task to exit. You can check with ps -axf what
> processes appeared and in which state. The -d (--restore-detached) option
> can help to handle this.
>
> > imgs_py/restore_py.log says:
> > (00.000661) Error (include/util.h:51): Can't write img file: Operation
> not permitted
>
> Can you show the full restore-py.log file? On restore the only file written
> should be the restore stats one.
>
> Thanks,
> Pavel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140105/1d999c4c/attachment.html>