<div dir="ltr">Thanks for clarifying this. This makes sense to me.<div><br></div><div>Before I write my own post-restore script, does criu have such script included?<br><div><br></div><div>- Hui<br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Aug 16, 2015 at 9:23 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 08/16/2015 10:12 PM, Hui Kang wrote:<br>
> Hi, Pavel<br>
> I used "--veth-pair veth101=veth100" when dumping and restoring a process. veth101 is the<br>
> device name in the process net namespace, veth100 is the other end which is in the criu host.<br>
><br>
> After restore, I can see the ip address of veth101 is restored. However, the veth end in the<br>
> host (veth100) is not successfully restored. By "not success", I mean the veth100 link is<br>
> created, however, its state is DOWN and no IP is assigned to the restore link. Only I manually<br>
> set the link state to UP and assigne IP, the two ends can talk to each other.<br>
<br>
</span>Yup, this is the host-side of the link. CRIU only manages the container side. If you need<br>
to do some configuration of the host-side part before the resume, you can hook in to the<br>
post-restore action script.<br>
<span class=""><br>
> Moreover, the link index of veth100 is not the same as when I dump the process. For example<br>
> the index for veth101 and veth100 is 15 and 16 when I dump the process. After restore,<br>
> veth100's index becomes 17. Is this a bug in CRIU? Thanks.<br>
<br>
</span>No, it's not a bug. The problem is that when you do the host-side link restore the index<br>
of it can be busy, so we don't even try to preserve it. Even if we do the "best-effort"<br>
attempt, it will succeed only in trivial cases.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Pavel<br>
<br>
</font></span></blockquote></div><br></div></div></div></div>