From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lucas Meneghel Rodrigues Subject: qemu and qemu.git -> Migration + disk stress introduces qcow2 corruptions Date: Wed, 09 Nov 2011 14:29:28 -0200 Message-ID: <4EBAAA68.10801@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: QEMU devel , KVM mailing list , Avi Kivity , Marcelo Tosatti , Anthony Liguori Received: from mx1.redhat.com ([209.132.183.28]:8612 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751285Ab1KIQ3a (ORCPT ); Wed, 9 Nov 2011 11:29:30 -0500 Sender: kvm-owner@vger.kernel.org List-ID: 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. Thanks, Lucas