[CRIU] [Users] criu check doesn't like the openvz kernel

[jjs - mainphrame]

Thanks for the feedback. Two thoughts come to mind:

1. criu check was complaining about the openvz kernel, not mainline

2. Are you saying that live migration should work, despite the indicated
kernel issues?

Whenever things get to the point that live migration (heck, even dead
migration at this point) ought to have a chance of working, I'll bring up
another openvz host and give it a try.


Regards,

Joe

On Sun, Sep 13, 2015 at 1:54 AM, Cyrill Gorcunov <gorcunov at gmail.com> wrote:

> On Sat, Sep 12, 2015 at 09:09:15PM -0700, Kir Kolyshkin wrote:
> >    It's better to ask this on a CRIU list (adding it).
> >
> >    On 09/12/2015 04:59 PM, jjs - mainphrame wrote:
> >
> >      Greetings,
> >      I gather there are still some fixes to be applied before migration
> will
> >      work properly. Just out of curiosity, do any or all of the issues
> below
> >      constitute a show stopper?
> >      [root at hachi ~]# criu check
> >      prctl: PR_SET_MM_MAP is not supported, which is required for
> restoring
> >      user namespaces
> >      Error (cr-check.c:602): Kernel doesn't support
> PTRACE_O_SUSPEND_SECCOMP
> >      Error (cr-check.c:703): AIO remap doesn't work properly
> >      Error (cr-check.c:719): fdinfo doesn't contain the lock field
> >      Error (cr-check.c:749): CLONE_PARENT | CLONE_NEWPID don't work
> together
> >      [root at hachi ~]# uname -a
> >      Linux hachi.mainphrame.net 3.10.0-123.1.2.vz7.5.29 #1 SMP Fri Jul
> 24
> >      18:45:12 MSK 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> Neither of this is critical as far as I can say. The things are that we
> don't
> yet ported all mainline commits to our kernel so here are check complains.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20150913/4d494e74/attachment.html>