From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 8AAA13F9 for ; Tue, 15 Dec 2015 09:23:24 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga102.fm.intel.com with ESMTP; 15 Dec 2015 00:23:23 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,431,1444719600"; d="scan'208";a="871716536" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.66.49]) by orsmga002.jf.intel.com with ESMTP; 15 Dec 2015 00:23:22 -0800 Date: Tue, 15 Dec 2015 16:23:24 +0800 From: Yuanhan Liu To: Peter Xu Message-ID: <20151215082324.GG29571@yliu-dev.sh.intel.com> References: <000001d133ed$b2446eb0$16cd4c10$@samsung.com> <20151211094934.GX29571@yliu-dev.sh.intel.com> <001c01d133fd$d3a7d870$7af78950$@samsung.com> <20151214035842.GB18437@pxdev.xzpeter.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151214035842.GB18437@pxdev.xzpeter.org> User-Agent: Mutt/1.5.21 (2010-09-15) 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:23:25 -0000 On Mon, Dec 14, 2015 at 11:58:42AM +0800, Peter Xu wrote: > On Fri, Dec 11, 2015 at 01:22:23PM +0300, Pavel Fedin wrote: > > BTW, it works, and it was my bad. openvswitch was configured incorrectly on the other side, vhost port number was different for > > some reason, while ruleset was the same. I reconfigured it and now everything migrates correctly, except increased downtime because > > of missing GARP (the guest misses some PINGs, then it retries ARP, which brings the link back up). > > Hi, > > When doing the ping, was it from the guest (to another host) or to > the guest (from another host)? > > In any case, I still could not understand why the ping loss happened > in this test. > > If ping from guest, no ARP refresh is required at all? > > 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? --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