From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Xu Subject: Re: [PATCH 0/4 for 2.3] vhost-user live migration support Date: Tue, 15 Dec 2015 17:42:54 +0800 Message-ID: <20151215094254.GC32243@pxdev.xzpeter.org> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: dev@dpdk.org To: Yuanhan Liu Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id B6A2D952 for ; Tue, 15 Dec 2015 10:43:03 +0100 (CET) Content-Disposition: inline In-Reply-To: <20151215082324.GG29571@yliu-dev.sh.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Dec 15, 2015 at 04:23:24PM +0800, Yuanhan Liu wrote: > On Mon, Dec 14, 2015 at 11:58:42AM +0800, Peter Xu wrote: > > If ping to guest from outside, when the migration finishes on the > > target side of qemu, qemu_self_announce() will be called. > > It's supposed to see some ARP requests if I run tcpdump against > with the ovs bridge, right? However, in fact, I saw nothing from > tcpdump on the target host when the migration is done. > > 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? AFAIK, it should be RARP rather than ARP request. However, sorry that I do not know the reason for its lossing either. Btw, I did a very basic live migration using v1 patchset locally today (one host, two QEMU instances attach to the same vhost-user socket), it's working too on my host. :) Thanks. Peter > > --yliu > > > Although > > we might see a warning like "Vhost user backend fails to broadcast > > fake RARP" (notify is done by hacking vhost_user_receive(), even if > > notify fails, things will still move on), QEMU should still send a > > RARP onto the link. > > > > Not sure whether I missed anything. > > > > Thanks. > > Peter