summary refs log tree commit diff stats
path: root/gitlab/issues/target_missing/host_missing/accel_missing/1997.toml
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-05-21 21:21:26 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-05-21 21:21:26 +0200
commit4b927bc37359dec23f67d3427fc982945f24f404 (patch)
tree245449ef9146942dc7fffd0235b48b7e70a00bf2 /gitlab/issues/target_missing/host_missing/accel_missing/1997.toml
parentaa8bd79cec7bf6790ddb01d156c2ef2201abbaab (diff)
downloadqemu-analysis-4b927bc37359dec23f67d3427fc982945f24f404.tar.gz
qemu-analysis-4b927bc37359dec23f67d3427fc982945f24f404.zip
add gitlab issues in toml format
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/1997.toml')
-rw-r--r--gitlab/issues/target_missing/host_missing/accel_missing/1997.toml28
1 files changed, 28 insertions, 0 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1997.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1997.toml
new file mode 100644
index 000000000..a307a7557
--- /dev/null
+++ b/gitlab/issues/target_missing/host_missing/accel_missing/1997.toml
@@ -0,0 +1,28 @@
+id = 1997
+title = "Disk corruption on ARM64 (Apple Silicon) Linux VMs"
+state = "opened"
+created_at = "2023-11-22T15:43:27.278Z"
+closed_at = "n/a"
+labels = ["Storage", "hostos: macOS"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1997"
+host-os = "macOS Sonoma 14.1.1"
+host-arch = "ARM / arm64 / aarch64"
+qemu-version = "7.2.0"
+guest-os = "Linux (any flavor).  In this particular case, Ubuntu 22.04 with HWE kernel"
+guest-arch = "arm / arm64/ aarch64"
+description = """aarch64 Linux VMs will encounter disk corruption if they're set up with a filesystem that will notice it when it happens, e.g. BTRFS.  This seems to be across the board with products, including Apple Hypervisor Framework, or just QEMU, so it very well might be an aarch64 Linux bug."""
+reproduce = """1. Install an aarch64 Linux VM using BTRFS as the root filesystem.  ZFS might recognize silent corruption readily as well.
+2. Run `stress-ng --iomix 4`
+3. Check your `dmesg` and/or `btrfs check --force <device>` to check for filesystem corruption."""
+additional = """This is discussed in two other tickets, but I'm hoping to get more attention to the problem here.
+[https://github.com/lima-vm/lima/issues/1957](https://github.com/lima-vm/lima/issues/1957)
+[](https://github.com/utmapp/UTM/issues/4840)
+
+![Screenshot_2023-11-22_at_10.20.23_AM](/uploads/ae8ed51c7adb59933c4f7f9673dddd3d/Screenshot_2023-11-22_at_10.20.23_AM.png)
+
+![Screenshot_2023-11-22_at_10.20.23_AM](https://i.imgur.com/HwqrFQE.png)
+
+I can't seem to figure out how to upload images, but you can probably get to the image that I'm trying to share somehow...
+
+
+```"""