<div dir="ltr">In actually,I have done as you said but there are no pid info in fdinfo-img,just id,flag,type and fd.<div><br></div><div><div><div><div>root@dslab:/home/dslab/tools/criu# ./crit show /home/checkpoint/c2/fdinfo-4.img </div><div>{</div><div> "magic": "FDINFO", </div><div> "entries": [</div><div> {</div><div> "id": 56, </div><div> "flags": 0, </div><div> "type": "REG", </div><div> "fd": 0</div><div> }, </div><div> {</div><div> "id": 57, </div><div> "flags": 0, </div><div> "type": "REG", </div><div> "fd": 1</div><div> }, </div><div> {</div><div> "id": 58, </div><div> "flags": 0, </div><div> "type": "REG", </div><div> "fd": 2</div><div> }, </div><div> {</div><div> "id": 59, </div><div> "flags": 1, </div><div> "type": "UNIXSK", </div><div> "fd": 3</div><div> }, </div><div> {</div><div> "id": 60, </div><div> "flags": 0, </div><div> "type": "REG", </div><div> "fd": 4</div><div> }, </div><div> {</div><div> "id": 61, </div><div> "flags": 1, </div><div> "type": "PACKETSK", </div><div> "fd": 5</div><div> }, </div><div> {</div><div> "id": 62, </div><div> "flags": 1, </div><div> "type": "INETSK", </div><div> "fd": 6</div><div> }, </div><div> {</div><div> "id": 63, </div><div> "flags": 0, </div><div> "type": "INETSK", </div><div> "fd": 20</div><div> }, </div><div> {</div><div> "id": 64, </div><div> "flags": 0, </div><div> "type": "INETSK", </div><div> "fd": 21</div><div> }</div><div> ]</div><div>}</div></div><div><br></div><div><div>In <span style="font-size:14px">packetsk.</span><span style="font-size:14px">img, there are the pid under "fown",It's the pid which I look for ?</span></div><div><br></div><div><div style="font-size:14px">root@dslab:/home/dslab/tools/criu# ./crit show /home/checkpoint/c2/packetsk.img </div><div style="font-size:14px">{</div><div style="font-size:14px"> "magic": "PACKETSK", </div><div style="font-size:14px"> "entries": [</div><div style="font-size:14px"> {</div><div style="font-size:14px"> "id": 61, </div><div style="font-size:14px"> "type": 10, </div><div style="font-size:14px"> "protocol": 768, </div><div style="font-size:14px"> "flags": "0x80002", </div><div style="font-size:14px"> "ifindex": 73, </div><div style="font-size:14px"> "fown": {</div><div style="font-size:14px"> "uid": 0, </div><div style="font-size:14px"> "euid": 0, </div><div style="font-size:14px"> "signum": 0, </div><div style="font-size:14px"> "pid_type": 0, </div><div style="font-size:14px"> "pid": 0</div><div style="font-size:14px"> }, </div><div><div>...</div><div>}</div></div></div></div></div></div><div><br></div><div>In the checkpoint dir,there are several core-$pid.img:</div><div><div>root@dslab:/home/checkpoint# ls c2/core-*</div><div>c2/core-1.img c2/core-20.img c2/core-68.img c2/core-89.img c2/core-90.img c2/core-92.img</div></div><div><br></div><div>So I grep each core img</div><div><div>root@dslab:/home/dslab/tools/criu# ./crit show /home/checkpoint/c2/core-1.img | grep comm</div><div> "comm": "systemd", </div><div>root@dslab:/home/dslab/tools/criu# ./crit show /home/checkpoint/c2/core-20.img | grep comm</div><div> "comm": "systemd-journal", </div><div>root@dslab:/home/dslab/tools/criu# ./crit show /home/checkpoint/c2/core-68.img | grep comm</div><div> "comm": "dhclient", </div><div>root@dslab:/home/dslab/tools/criu# ./crit show /home/checkpoint/c2/core-89.img | grep comm</div><div> "comm": "sshd", </div><div>root@dslab:/home/dslab/tools/criu# ./crit show /home/checkpoint/c2/core-90.img | grep comm</div><div> "comm": "rc.local", </div><div>root@dslab:/home/dslab/tools/criu# ./crit show /home/checkpoint/c2/core-92.img | grep comm</div><div> "comm": "a.out", </div></div><div><br></div><div>a.out is just the test app without network usage.Maybe something wrong exist in other processes?</div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-10-16 2:10 GMT+08:00 Tycho Andersen <span dir="ltr"><<a href="mailto:tycho.andersen@canonical.com" target="_blank">tycho.andersen@canonical.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Oct 15, 2015 at 08:37:02PM +0800, Jason Lee wrote:<br>
> In this server,I only run the latest version LXC and CRIU. There are no any<br>
> my own applications<br>
> using socket in LXC(maybe sshd or dhclient?).My distribution linux is<br>
> debian 8<br>
> so I don't know which applications use SOCK_PACKET ...<br>
<br>
</span>If you look to see which pid (crit show fdinfo-$pid.img) has an fd<br>
info with the id 61 (your SOCK_PACKET socket), you can get the command<br>
name from core.img (crit show core-$pid.img | grep comm). I'd be<br>
curious to know what application this is, because it if is something<br>
like systemd, it will come downstream to ubuntu and we'll need to fix<br>
this soon :)<br>
<span class="HOEnZb"><font color="#888888"><br>
Tycho<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> To avoid this situation, I think using two network card is better than<br>
> net-bridge,isn't it ?<br>
><br>
> I wish criu could solve this issue in next version!<br>
><br>
><br>
> - Jason<br>
><br>
> 2015-10-15 20:08 GMT+08:00 Jason Lee <<a href="mailto:ldm5235@gmail.com">ldm5235@gmail.com</a>>:<br>
><br>
> ><br>
> > ---------- Forwarded message ----------<br>
> > From: Pavel Emelyanov <<a href="mailto:xemul@parallels.com">xemul@parallels.com</a>><br>
> > Date: 2015-10-15 20:06 GMT+08:00<br>
> > Subject: Re: [CRIU] lxc-checkpoint restore failed<br>
> > To: Jason Lee <<a href="mailto:ldm5235@gmail.com">ldm5235@gmail.com</a>><br>
> > Cc: Tycho Andersen <<a href="mailto:tycho.andersen@canonical.com">tycho.andersen@canonical.com</a>>, <a href="mailto:criu@openvz.org">criu@openvz.org</a><br>
> ><br>
> ><br>
> > On 10/15/2015 03:04 PM, Pavel Emelyanov wrote:<br>
> > > On 10/15/2015 02:58 PM, Jason Lee wrote:<br>
> > >> OK!<br>
> > >> Here it is:<br>
> > >><br>
> > >> root@dslab:/home/dslab/tools/criu# ./crit show<br>
> > /home/checkpoint/c2/packetsk.img<br>
> > >> {<br>
> > >> "magic": "PACKETSK",<br>
> > >> "entries": [<br>
> > >> {<br>
> > >> "id": 61,<br>
> > >> "type": 10,<br>
> > ><br>
> > > Here it is. This is SOCK_PACKET which we didn't support (and didn't put<br>
> > check<br>
> > > for it on dump). Which software uses this thing? AF_PACKET sockets are<br>
> > typically<br>
> > > SOCK_RAW or SOCK_DGRAM, SOCK_PACKET is, frankly speaking, new to me :)<br>
> ><br>
> > Just FIY, I've created an issue for this feature:<br>
> > <a href="https://github.com/xemul/criu/issues/73" rel="noreferrer" target="_blank">https://github.com/xemul/criu/issues/73</a><br>
> ><br>
> > -- Pavel<br>
> ><br>
> ><br>
</div></div></blockquote></div><br></div>