<div dir="ltr">Thanks guys-- I will make sure to direct OpenVZ questions to this list.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 14, 2015 at 11:16 AM, Kir Kolyshkin <span dir="ltr"><<a href="mailto:kir@openvz.org" target="_blank">kir@openvz.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
On 07/14/2015 04:39 AM, Pavel Emelyanov wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 07/14/2015 12:01 AM, Divjyot sethi wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello Pavel,<br>
I have an OpenVZ container setup which I can live mgrate. However, I need to run another process<br>
in it and migrate that too. This process accesses a special device which I install on host node<br>
and setup a driver for it (a dynamic kernel module). Turns out that this process can not access<br>
the loaded kernel module on the host node. Can you please let me know the steps for doing this?<br>
</blockquote>
For openvz containers this is usually done by the vzctl --devnodes option. Plz, refer to<br>
vzctl docs for that. For other openvz questions is better to go to <a href="mailto:devel@openvz.org" target="_blank">devel@openvz.org</a> mailing<br>
list, not to CRIU one :)<br>
</blockquote>
<br></div></div>
I would say, users@ not devel@<br>
<br>
</blockquote></div><br></div>