summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2/output/hypervisor/649
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/deepseek-2/output/hypervisor/649
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2/output/hypervisor/649')
-rw-r--r--results/classifier/deepseek-2/output/hypervisor/6499
1 files changed, 9 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2/output/hypervisor/649 b/results/classifier/deepseek-2/output/hypervisor/649
new file mode 100644
index 000000000..90a36810a
--- /dev/null
+++ b/results/classifier/deepseek-2/output/hypervisor/649
@@ -0,0 +1,9 @@
+
+qemu-6.1.0 causes I/O errors in VMs leading to data corruption
+Description of problem:
+after upgrading around 10 gentoo hosts from qemu-6.0.0-r53 to 6.1.0 most VMs (around 85 of 100, our VMs with PostgreSQL have 100% chance of hitting this) after some time (few minutes) will have I/O Errors, causing crashes and data corruption.
+The VMs are stored on ZFS volumes.
+Downgrading to qemu-6.0.0-r53 instantly fixes this.
+Happens on completely different hardware (quad core Xeons to 32C Epyc2).
+
+Reproducible: Always