From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lucas Meneghel Rodrigues Subject: Re: qemu and qemu.git -> Migration + disk stress introduces qcow2 corruptions Date: Wed, 09 Nov 2011 21:33:14 -0200 Message-ID: <4EBB0DBA.80107@redhat.com> References: <4EBAAA68.10801@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: QEMU devel , KVM mailing list , Avi Kivity , Marcelo Tosatti , Anthony Liguori , Kevin Wolf , "Michael S. Tsirkin" To: quintela@redhat.com Return-path: Received: from mx1.redhat.com ([209.132.183.28]:51879 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751617Ab1KIXdP (ORCPT ); Wed, 9 Nov 2011 18:33:15 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 11/09/2011 05:25 PM, Juan Quintela wrote: > Lucas Meneghel Rodrigues wrote: >> Hi guys, here I am, reporting yet another issue with qemu. This time, >> it's something that was first reported in January, and Juan proposed a >> patch for it: >> >> http://comments.gmane.org/gmane.comp.emulators.qemu/89009 >> >> [PATCH 4/5] Reopen files after migration >> >> The symptom is, when running disk stress or any intense IO operation >> in guest while migrating it causes a qcow2 corruption. We've seen this >> consistently on the daily test jobs, both for qemu and qemu-kvm. The >> test that triggers it is autotest stress test running on a VM with >> ping-pong background migration. >> >> The fix proposed by Juan is on our RHEL branch and such a problem does >> not happen on the RHEL branch. So, what about re-considering Juan's >> patch, or maybe work out a solution that is satisfactory for the >> upstream maintainers? >> >> I'll open a launchpad bug with this report. > > I have just sent: > > [RFC PATCH 0/2] Fix migration with NFS& iscsi/Fiber channel > > Only the 1st patch on that series are needed to fix that problem. Could > you try it? Just tried it, it conclusively fixes the corruption problems. Reported it on the patch email. > Thanks, Juan. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:45802) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ROHds-0004lY-Vm for qemu-devel@nongnu.org; Wed, 09 Nov 2011 18:33:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ROHdr-0007Co-Kf for qemu-devel@nongnu.org; Wed, 09 Nov 2011 18:33:16 -0500 Received: from mx1.redhat.com ([209.132.183.28]:14208) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ROHdr-0007Aa-CE for qemu-devel@nongnu.org; Wed, 09 Nov 2011 18:33:15 -0500 Message-ID: <4EBB0DBA.80107@redhat.com> Date: Wed, 09 Nov 2011 21:33:14 -0200 From: Lucas Meneghel Rodrigues MIME-Version: 1.0 References: <4EBAAA68.10801@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] qemu and qemu.git -> Migration + disk stress introduces qcow2 corruptions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: quintela@redhat.com Cc: Kevin Wolf , KVM mailing list , "Michael S. Tsirkin" , Marcelo Tosatti , QEMU devel , Avi Kivity On 11/09/2011 05:25 PM, Juan Quintela wrote: > Lucas Meneghel Rodrigues wrote: >> Hi guys, here I am, reporting yet another issue with qemu. This time, >> it's something that was first reported in January, and Juan proposed a >> patch for it: >> >> http://comments.gmane.org/gmane.comp.emulators.qemu/89009 >> >> [PATCH 4/5] Reopen files after migration >> >> The symptom is, when running disk stress or any intense IO operation >> in guest while migrating it causes a qcow2 corruption. We've seen this >> consistently on the daily test jobs, both for qemu and qemu-kvm. The >> test that triggers it is autotest stress test running on a VM with >> ping-pong background migration. >> >> The fix proposed by Juan is on our RHEL branch and such a problem does >> not happen on the RHEL branch. So, what about re-considering Juan's >> patch, or maybe work out a solution that is satisfactory for the >> upstream maintainers? >> >> I'll open a launchpad bug with this report. > > I have just sent: > > [RFC PATCH 0/2] Fix migration with NFS& iscsi/Fiber channel > > Only the 1st patch on that series are needed to fix that problem. Could > you try it? Just tried it, it conclusively fixes the corruption problems. Reported it on the patch email. > Thanks, Juan.