From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Lalancette Subject: Re: Live Migration fails Date: Wed, 30 Jul 2008 09:11:16 +0200 Message-ID: <48901414.6050603@redhat.com> References: <488F88BE.1090504@hasware.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Daniel Hasler Return-path: Received: from mx1.redhat.com ([66.187.233.31]:55066 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751580AbYG3HMt (ORCPT ); Wed, 30 Jul 2008 03:12:49 -0400 In-Reply-To: <488F88BE.1090504@hasware.ch> Sender: kvm-owner@vger.kernel.org List-ID: Daniel Hasler wrote: > After a while, on host B (the target), I see the following error: > >migration: wait_for_go: read error len=0 (Interrupted system call) > >Migration failed rc=210 > > while on host A, I read following error message: > >WAIT FOR ACK: timeout reached > >Migration failed! ret=0 error=13 No, this is a bug I just fixed yesterday in Qemu proper. The next time that Avi rebases KVM to Qemu (which he said he would do as soon as the fix went into Qemu), then this should be fixed. FYI, the problem is basically that the i2c restore on the destination side was expecting 4 bytes, while the i2c save on the sending side was only sending 1 byte, so they eventually timed out while waiting for each other. Chris Lalancette