[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 888150] [NEW] qemu and qemu.git -> Migration + disk st
From: |
Lucas Meneghel Rodrigues |
Subject: |
[Qemu-devel] [Bug 888150] [NEW] qemu and qemu.git -> Migration + disk stress introduces qcow2 corruptions |
Date: |
Wed, 09 Nov 2011 16:30:52 -0000 |
Public bug reported:
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?
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/888150
Title:
qemu and qemu.git -> Migration + disk stress introduces qcow2
corruptions
Status in QEMU:
New
Bug description:
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?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/888150/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |