qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] scp during migration with vhost fails
Date: Sun, 3 Feb 2013 11:22:36 +0200	[thread overview]
Message-ID: <20130203092236.GA1813@redhat.com> (raw)
In-Reply-To: <2881193.PTWX93cU7x@jason-thinkpad-t430s>

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

      reply	other threads:[~2013-02-03  9:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 10:03 [Qemu-devel] scp during migration with vhost fails Jason Wang
2013-02-03  9:22 ` Michael S. Tsirkin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130203092236.GA1813@redhat.com \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).