summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/files/888150
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/files/888150
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/files/888150')
-rw-r--r--results/classifier/gemma3:12b/files/88815012
1 files changed, 12 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/files/888150 b/results/classifier/gemma3:12b/files/888150
new file mode 100644
index 000000000..7571c2e38
--- /dev/null
+++ b/results/classifier/gemma3:12b/files/888150
@@ -0,0 +1,12 @@
+
+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?
\ No newline at end of file