From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout2.w1.samsung.com (mailout2.w1.samsung.com [210.118.77.12]) by dpdk.org (Postfix) with ESMTP id 1E1BB256 for ; Tue, 15 Dec 2015 09:45:59 +0100 (CET) Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout2.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0NZE00F8Q5OL8840@mailout2.w1.samsung.com> for dev@dpdk.org; Tue, 15 Dec 2015 08:45:57 +0000 (GMT) X-AuditID: cbfec7f5-f79b16d000005389-0c-566fd345663c Received: from eusync2.samsung.com ( [203.254.199.212]) by eucpsbgm2.samsung.com (EUCPMTA) with SMTP id B1.1C.21385.543DF665; Tue, 15 Dec 2015 08:45:57 +0000 (GMT) Received: from fedinw7x64 ([106.109.131.169]) by eusync2.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0NZE00LXV5OKYX30@eusync2.samsung.com>; Tue, 15 Dec 2015 08:45:57 +0000 (GMT) From: Pavel Fedin To: 'Yuanhan Liu' , 'Peter Xu' References: <000001d133ed$b2446eb0$16cd4c10$@samsung.com> <20151211094934.GX29571@yliu-dev.sh.intel.com> <001c01d133fd$d3a7d870$7af78950$@samsung.com> <20151214035842.GB18437@pxdev.xzpeter.org> <20151215082324.GG29571@yliu-dev.sh.intel.com> In-reply-to: <20151215082324.GG29571@yliu-dev.sh.intel.com> Date: Tue, 15 Dec 2015 11:45:56 +0300 Message-id: <007f01d13715$042a0a80$0c7e1f80$@samsung.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AQOYHvn87qB/n3eE/cMtloPRrGw32gEpxH/xAfOP4FMB9WC4FAK9V+xZmv9rBNA= Content-language: ru X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrELMWRmVeSWpSXmKPExsVy+t/xK7qul/PDDF7dULF492k7k8WW/d/Y La5PuMDqwOzxa8FSVo95JwM93u+7yhbAHMVlk5Kak1mWWqRvl8CV0XLxCFvBItaKTZ9fMTYw TmLpYuTkkBAwkXh8s4MVwhaTuHBvPVsXIxeHkMBSRomb2x8zQzjfGSUu/lnCDlLFJqAucfrr B7BuEQF/iVvnNoDFmQUEJB7fe8YK0fCDUeLIuglgCU4Ba4kHN3cxgtjCAr4SL5c+YQKxWQRU JU62fQdq4ODgFbCUaLnlDBLmFRCU+DH5HgvETC2J9TuPM0HY8hKb17xlhrhUQWLH2deMEDf4 SRzetZAVokZEYtq/e8wTGIVmIRk1C8moWUhGzULSsoCRZRWjaGppckFxUnqukV5xYm5xaV66 XnJ+7iZGSMh/3cG49JjVIUYBDkYlHt4FzPlhQqyJZcWVuYcYJTiYlUR4T54BCvGmJFZWpRbl xxeV5qQWH2KU5mBREueduet9iJBAemJJanZqakFqEUyWiYNTqoExY0pEvd+3lnJ/kzfLOZii LC9fMul/xybknVdUsvv6v7ivhbfU3y6zmbZXZ+LWhyxcAlZ2kRO//dvkVHfISvPMvZjpwTea Vvaf3sSdsOMbz/ZoRhbRhcuXJ5ioWwkp+7HfeDc3Iy9whevxVxKZUyXOHFdI02VanNf+fX4U X84KhYxdba+lXwYpsRRnJBpqMRcVJwIAO154y3UCAAA= Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 0/4 for 2.3] vhost-user live migration support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2015 08:45:59 -0000 Hello! > I mean I do find that qemu_annouce_self composes an ARP > broadcoast request, but it seems that I didn't catch it on > the target host. > > Something wrong, or someting I missed? To tell the truth, i don't know. I am also learning qemu internals on the fly. Indeed, i see that it should announce itself. But this brings up a question: why do we need special announce procedure in vhost-user then? I think you can add some debug output and see how it works in realtime. This is what i normally do when i don't understand in which sequence things happen. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia