<div dir="ltr"><div>Thanks Pavel and CRIU community!</div><div><br></div><div>As per plan, I have started learning code, CRIT tool and running up zdtm test as pointed.</div><div><br></div><div>Regards,</div><div>Abhishek<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 7, 2019 at 7:24 PM Pavel Emelianov <<a href="mailto:xemul@virtuozzo.com">xemul@virtuozzo.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">Abhishek,<br>
<br>
Let me first congratulate you on being accepted to this year's GSoC project :)<br>
<br>
Please meet Andrey and Mike, they will be helping me drive the pre-dump rework<br>
during this summer.<br>
<br>
According to your plan, the upcoming 3 weeks you're about to spend learning the<br>
code, the CRIT tool and getting familiar with the patch/PR submission process, so<br>
my question is -- is everything going fine with that?<br>
<br>
Also, as the project is about pre-dump, you should know how to do the pre-dump<br>
itself :) I suggest you to prepare an experimental stand that does this:<br>
<br>
a) launch a zdtm test by name<br>
b) do some pre-dump steps on it<br>
c) do the final dump<br>
d) try to restore from the images<br>
e) check the restore was OK<br>
<br>
i.e. -- a light version of live-migration. You can pick the test/jenkins/criu-pre-dump.sh<br>
script as a source of inspiration and make it work from plain shell (not from jeknins<br>
piplines). Having this stand at hands we will be able to compare the correctness and <br>
efficiency of your changes.<br>
<br>
-- Pavel<br>
</blockquote></div>