From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id DB8652EDA for ; Mon, 14 Dec 2015 10:04:18 +0100 (CET) Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id C13514C394; Mon, 14 Dec 2015 09:04:17 +0000 (UTC) Received: from pxdev.xzpeter.org (vpn1-6-34.pek2.redhat.com [10.72.6.34]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tBE948CZ015032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 14 Dec 2015 04:04:13 -0500 Date: Mon, 14 Dec 2015 17:04:06 +0800 From: Peter Xu To: Pavel Fedin Message-ID: <20151214090406.GC18437@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> <00c401d13641$5e53cf20$1afb6d60$@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <00c401d13641$5e53cf20$1afb6d60$@samsung.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 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: Mon, 14 Dec 2015 09:04:19 -0000 On Mon, Dec 14, 2015 at 10:30:54AM +0300, Pavel Fedin wrote: > Hello! Hi, Pavel! > > > 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? > > ping from guest to host. > > Ok, my setup was: > > Host<------->openVSwitch<----------->guest > LOCAL vhostuser > > So, in order to migrate the guest, i simply replicated this setup on both hosts, with the same IPs on host side. And on both hosts i set up the following ruleset for openvswitch: Regarding to "with the same IPs on host side": do you mean that you configured the same IP on two hosts in the intranet? I think this does not matter if we are testing it functionally (whether live migration could work), However I would still perfer to try ping another host (say, host3) inside the intranet. What do you think? When pinging host3, I assume there should have no ping loss. Also, should have no loss too in the revert direction (reason as in previous mail). > > ovs-ofctl add-flow ovs-br0 in_port=1,actions=output:LOCAL > ovs-ofctl add-flow ovs-br0 in_port=LOCAL,actions=output:1 > > And on the second host, for some reason, vhostuser port got no 2 in the database instead of 1. Probably because first i added wrong port, then added correct one, then removed the wrong one. So, as i wrote before - please don't worry, the patch works fine, it was totally my lame fault. Yes, thanks to let me know that the patch is working. Actually what I am interested in is the down time that when host3 ping guest from outside during migration. Would you please let me know the result if you are doing such tests in the future? And please just ignore this if there is no requirement on your side. Thanks! Peter