<div dir="ltr">Hi dmitry,<div><br></div><div>VM is yours, will ask you again before taking it down, in about a week or so.</div><div><br></div><div>thanks,</div><div>Shlomi. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 30, 2018 at 3:09 PM, Dmitry Safonov <span dir="ltr"><<a href="mailto:0x7f454c46@gmail.com" target="_blank">0x7f454c46@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Shlomi,<br>
<span class=""><br>
2018-01-30 8:40 GMT+00:00 Shlomi Matichin <<a href="mailto:shlomi@binaris.com">shlomi@binaris.com</a>>:<br>
> hi andrei,<br>
><br>
> i've confirmed it to work on latest unstable ubuntu kernel (installed on the<br>
> test VM). thanks a lot for your help!<br>
><br>
> do you still need the VM, or can i take it down?<br>
<br>
</span>If it's not a big price for you - we would like to have it still on at<br>
least till<br>
the next Monday. The thing is that we still advertise that criu supports<br>
kernel up from v3.10. So, in my opinion, we should either create a<br>
workaround or correct <a href="http://criu.org" rel="noreferrer" target="_blank">criu.org</a> and say that we support Skylake platform<br>
only from v4.14. In any case we kinda interested in what was broken.<br>
What do you think, Andrey?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Dmitry<br>
</font></span></blockquote></div><br></div>