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