blob: e7020f9293cd456221a0a574a4f99dabd213ce09 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
files: 0.922
virtual: 0.859
device: 0.839
mistranslation: 0.797
graphic: 0.791
architecture: 0.766
hypervisor: 0.741
performance: 0.728
network: 0.697
semantic: 0.696
vnc: 0.652
permissions: 0.651
peripherals: 0.642
debug: 0.637
ppc: 0.637
kernel: 0.588
x86: 0.559
socket: 0.558
VMM: 0.511
user-level: 0.502
register: 0.499
TCG: 0.482
PID: 0.461
risc-v: 0.453
arm: 0.437
i386: 0.419
assembly: 0.415
boot: 0.337
KVM: 0.285
qemu and qemu.git -> Migration + disk stress introduces qcow2 corruptions
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?
The URL that you've mentioned in the description is not valid anymore ... can you still reproduce this problem with the latest version of QEMU, or can we close this ticket nowadays?
[Expired for QEMU because there has been no activity for 60 days.]
|