[CRIU] CRIU built without CONFIG_COMPAT - can't C/R compatible tasks

[Damodharan Mohanrajan]

Okay, Thank you so much for the clarification.

On Sat, Dec 28, 2019 at 12:05 AM Dmitry Safonov <0x7f454c46 at gmail.com>
wrote:

> Hi Damodharan,
>
> On 12/21/19 11:48 PM, Damodharan Mohanrajan wrote:
> > Dear team,
> >         I got an error message when i ran '$criu check --all' command. I
> > haveincluded the details as below. Please help me with this. I'm struck
> > on my university thesis and have to finish and submit by next week. A
> > great thanks to you for anyhelp you do. I'm ready to give any further
> > details from my side.
> >
> > Command: $ sudo criu check --all
> >
> > Error:
> > Warn  (criu/cr-check.c:850): Dirty tracking is OFF. Memory snapshot will
> > not work.
> > Warn  (criu/cr-check.c:1231): Do not have API to map vDSO - will use
> > mremap() to restore vDSO
> > Warn  (criu/cr-check.c:1199): CRIU built without CONFIG_COMPAT - can't
> > C/R compatible tasks
> > Looks good but some kernel features are missing
> > which, depending on your process tree, may cause
> > dump or restore failure.
>
> As Radostin pointed, those are optional features.
>
> >
> > Details are below:
> >
> > My device: Raspberry pi-4 (4GB version) (Arm64 based)
>
> The message you see means that CRIU doesn't support aarch32 applications
> C/R on arm64.
>
> Thanks,
>           Dmitry
>


-- 
Thanks & Regards
Damodharan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20191231/7484e3fb/attachment.html>