From 4b927bc37359dec23f67d3427fc982945f24f404 Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Wed, 21 May 2025 21:21:26 +0200 Subject: add gitlab issues in toml format --- .../host_missing/accel_missing/649.toml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 gitlab/issues/target_missing/host_missing/accel_missing/649.toml (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/649.toml') diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/649.toml b/gitlab/issues/target_missing/host_missing/accel_missing/649.toml new file mode 100644 index 00000000..7561f0d7 --- /dev/null +++ b/gitlab/issues/target_missing/host_missing/accel_missing/649.toml @@ -0,0 +1,20 @@ +id = 649 +title = "qemu-6.1.0 causes I/O errors in VMs leading to data corruption" +state = "opened" +created_at = "2021-09-29T17:41:09.971Z" +closed_at = "n/a" +labels = ["Storage"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/649" +host-os = "Gentoo Linux" +host-arch = "amd64" +qemu-version = "6.1.0" +guest-os = "Gentoo Linux" +guest-arch = "amd64" +description = """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""" +reproduce = "n/a" +additional = "n/a" -- cgit 1.4.1