From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:56710) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U1viO-0006Yf-Jt for qemu-devel@nongnu.org; Sun, 03 Feb 2013 04:18:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U1viM-0006mP-3Y for qemu-devel@nongnu.org; Sun, 03 Feb 2013 04:18:20 -0500 Received: from mx1.redhat.com ([209.132.183.28]:11380) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U1viL-0006mI-Rs for qemu-devel@nongnu.org; Sun, 03 Feb 2013 04:18:18 -0500 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 (8.14.4/8.14.4) with ESMTP id r139IG44027645 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 3 Feb 2013 04:18:16 -0500 Date: Sun, 3 Feb 2013 11:22:36 +0200 From: "Michael S. Tsirkin" Message-ID: <20130203092236.GA1813@redhat.com> References: <2881193.PTWX93cU7x@jason-thinkpad-t430s> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2881193.PTWX93cU7x@jason-thinkpad-t430s> Subject: Re: [Qemu-devel] scp during migration with vhost fails List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jason Wang Cc: qemu-devel@nongnu.org On Fri, Feb 01, 2013 at 06:03:32PM +0800, Jason Wang wrote: > Hello all: > > During testing, I find doing scp during migration with vhost fails with > warnings in guest like: > > Corrupted MAC on input. > Disconnecting: Packet corrupt. > lost connection > > Here's the bisect result: > > Commit a01672d3968cf91208666d371784110bfde9d4f8 kvm: convert to MemoryListener > API is the last commit that works well. > > With commit 04097f7c5957273c578f72b9bd603ba6b1d69e33 vhost: convert to > MemoryListener API, guest network is unusable with warning of "bad gso type" > > With commit d743c382861eaa1e13f503b05aba5a382a7e7f7c vhost: fix incorrect > userspace address, guest network is available, but scp during migration may > fail. > > Looks like the issue is related to memory api, any thoughts? > > Thanks Hmm this is worrying. The problem doesn't seem to reproduce for me. One explanation would be that the memory table is setup incorrectly, if this happens it's very worrying. I think a good way to debug would be by dumping the vhost tables before and after the change, verify that they are identical. -- MST