From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Qemu-KVM Livate Migration 0.12.2 -> 0.12.3/4 broken? Date: Mon, 17 May 2010 10:00:24 +0300 Message-ID: <4BF0E988.1040505@redhat.com> References: <4BE93882.8050105@dlh.net> <4BEFDEE1.5070906@redhat.com> <4BF00592.5040403@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Lieven , kvm@vger.kernel.org, qemu-devel@nongnu.org, Anthony Liguori To: Juan Quintela Return-path: Received: from mx1.redhat.com ([209.132.183.28]:11725 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753021Ab0EQHAf (ORCPT ); Mon, 17 May 2010 03:00:35 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 05/16/2010 11:04 PM, Juan Quintela wrote: > >>> So, to make the story short: I know what is happening, and I know how to >>> fix it, just that fix is not trivial. I just need time. >>> >>> >> Meanwhile, we have a broken 0.12.4. Is there a quick'n'dirty >> workaround that will be forward compatible with the real fix that we >> can push out? >> > revert the patch. It almost never happen (being in the middle of one > IO) while migrating. > If the guest does any work, it will always happen. > >> 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. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.