From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52586 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ODwIS-000740-8b for qemu-devel@nongnu.org; Mon, 17 May 2010 05:07:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1ODwIM-00054r-6f for qemu-devel@nongnu.org; Mon, 17 May 2010 05:07:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42645) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1ODwIL-00054j-Uo for qemu-devel@nongnu.org; Mon, 17 May 2010 05:07:30 -0400 From: Juan Quintela In-Reply-To: <4BF0FCEF.3060204@msgid.tls.msk.ru> (Michael Tokarev's message of "Mon, 17 May 2010 12:23:11 +0400") References: <4BE93882.8050105@dlh.net> <4BEFDEE1.5070906@redhat.com> <4BF00592.5040403@redhat.com> <4BF0E988.1040505@redhat.com> <4BF0FCEF.3060204@msgid.tls.msk.ru> Date: Mon, 17 May 2010 11:07:22 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Qemu-devel] Re: Qemu-KVM Livate Migration 0.12.2 -> 0.12.3/4 broken? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Tokarev Cc: Peter Lieven , Avi Kivity , kvm@vger.kernel.org, qemu-devel@nongnu.org Michael Tokarev wrote: > 17.05.2010 11:00, Avi Kivity wrote: >> On 05/16/2010 11:04 PM, Juan Quintela wrote: > [] >>>> We've regressed from failing some migrations to failing all migrations. >>> Humm, 0.12.4 -> 0.12.4 should work. My advise is just revert the patch >>> and live with it for another week, what do you think? >> >> A week is fine. I'm not going to release 0.12.4.1 for the week until you >> fix it, and just changing things in git doesn't help users. > > There are at least 1 other problem in the migration code that's > worth looking at (IMHO anyway): namely, migration on 32 bit host > is completely (as far as i can see) broken (instant kvm process > crash) in 0.12, but it works on 64bits: > > http://www.mail-archive.com/kvm@vger.kernel.org/msg34051.html > > I wonder why it is not noticed before -- it's broken since 0.12... People has become rich and everybody has a 64 bit hardware :-) Will take a look at the end of the week. Thank for the report, Juan.