From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Live Migration fails Date: Wed, 30 Jul 2008 09:36:35 -0500 Message-ID: <48907C73.8070906@codemonkey.ws> References: <488F88BE.1090504@hasware.ch> <48901414.6050603@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Hasler , kvm@vger.kernel.org To: Chris Lalancette Return-path: Received: from an-out-0708.google.com ([209.85.132.240]:4965 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751811AbYG3OhJ (ORCPT ); Wed, 30 Jul 2008 10:37:09 -0400 Received: by an-out-0708.google.com with SMTP id d40so6340and.103 for ; Wed, 30 Jul 2008 07:37:09 -0700 (PDT) In-Reply-To: <48901414.6050603@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Chris Lalancette wrote: > 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. > Migration is also known to be broken with virtio. Regards, Anthony Liguori > 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 > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >