<div dir="ltr">Hello Pavel,<br>I have an OpenVZ container setup which I can live mgrate. However, I need to run another process in it and migrate that too. This process accesses a special device which I install on host node and setup a driver for it (a dynamic kernel module). Turns out that this process can not access the loaded kernel module on the host node. Can you please let me know the steps for doing this?<br><br>Thanks,<br>Divjyot</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 23, 2015 at 2:21 PM, Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 06/22/2015 10:21 PM, Divjyot sethi wrote:<br>
> Hello Pavel,<br>
> Thanks for the help -- I was finaly able to do end-end live migration with Criu (version 1.5.2). I did not<br>
> remove the cgroups but just made sure that the directory structure at destination cgroup matched at the<br>
> source to make this work.<br>
<br>
</span>That's great news!<br>
<span class=""><br>
> One question: this works with Criu version 1.5.2. I had done some development with Criu version 1.3.1. In<br>
> order to be on a faster track, I was hoping to be able to use Criu version 1.3.1 for live migration -- do<br>
> you know if live migration could be made to work with that version? Currently I get an RPC error with that version -- .<br>
><br>
> Error: Exception: CRIU RPC error (0/8)<br>
> Error (cr-service.c:705): Can't recv request: Connection reset by peer<br>
<br>
</span>Well, we did p.haul first with 1.3, then criu has changed significantly. If it<br>
is still important for you to stay with 1.3 we can try to resolve why this got<br>
broken, but I suggest you to better switch on 1.6.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Pavel<br>
<br>
</font></span></blockquote></div><br></div>