<div dir="ltr">Okay, Thank you so much for the clarification. <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Dec 28, 2019 at 12:05 AM Dmitry Safonov <<a href="mailto:0x7f454c46@gmail.com">0x7f454c46@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Damodharan,<br>
<br>
On 12/21/19 11:48 PM, Damodharan Mohanrajan wrote:<br>
> Dear team,<br>
> I got an error message when i ran '$criu check --all' command. I<br>
> haveincluded the details as below. Please help me with this. I'm struck<br>
> on my university thesis and have to finish and submit by next week. A<br>
> great thanks to you for anyhelp you do. I'm ready to give any further<br>
> details from my side.<br>
> <br>
> Command: $ sudo criu check --all<br>
> <br>
> Error:<br>
> Warn (criu/cr-check.c:850): Dirty tracking is OFF. Memory snapshot will<br>
> not work.<br>
> Warn (criu/cr-check.c:1231): Do not have API to map vDSO - will use<br>
> mremap() to restore vDSO<br>
> Warn (criu/cr-check.c:1199): CRIU built without CONFIG_COMPAT - can't<br>
> C/R compatible tasks<br>
> Looks good but some kernel features are missing<br>
> which, depending on your process tree, may cause<br>
> dump or restore failure.<br>
<br>
As Radostin pointed, those are optional features.<br>
<br>
> <br>
> Details are below:<br>
> <br>
> My device: Raspberry pi-4 (4GB version) (Arm64 based)<br>
<br>
The message you see means that CRIU doesn't support aarch32 applications<br>
C/R on arm64.<br>
<br>
Thanks,<br>
Dmitry<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Thanks & Regards<br></div>Damodharan.<br></div></div></div></div>