Package: qemu-system-x86 Version: 1:10.0.7+ds-0+deb13u1+b1 Severity: important Tags: upstream
Hello! I'd like to leave a trace for others hitting this issue. QEMU 10.0.7, present in debian Trixie, has a bug leading to corruption of guest qcow2 image in the following scenario: * have qcow2 images for VM guest drives * have high ongoing disk IO activity within the guest during the steps below * virsh snapshot-create-as --domain VMNAME --name "kvmsnap-VMNAME" --no-metadata --atomic --disk-only vdX,external * wait a bit - during this time I'm running rsync to copy VM's qcow2 files * virsh blockcommit VMNAME vdX--active --pivot --verbose Corruption happens rarely, is not guaranteed to happen. Nevertheless others have seen it happening as well. Please see for ongoing discussion, so far there's no official fix. https://gitlab.com/qemu-project/qemu/-/issues/3273. Looks like it's a regression starting from qemu 8.2.0 affecting that and later releases. Possibly disabling default discard='unmap' might resolve it at the expense of faster wear of the underlying SSD/NVMe storage and performance. Thanks for maintenance of this package! -- System Information: Debian Release: 13.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.12.73+deb13-amd64 (SMP w/128 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qemu-system-x86 depends on: ii ipxe-qemu 1.21.1+git20250501.dad20602+dfsg-1 ii libaio1t64 0.3.113-8+b1 ii libbpf1 1:1.5.0-3 ii libc6 2.41-12+deb13u1 ii libcapstone5 5.0.6-1 ii libfdt1 1.7.2-2+b1 ii libfuse3-4 3.17.2-3 ii libglib2.0-0t64 2.84.4-3~deb13u2 ii libgmp10 2:6.3.0+dfsg-3 ii libgnutls30t64 3.8.9-3+deb13u2 ii libhogweed6t64 3.10.1-1 ii libibverbs1 56.1-1 ii libjpeg62-turbo 1:2.1.5-4 ii libnettle8t64 3.10.1-1 ii libnuma1 2.0.19-1 ii libpixman-1-0 0.44.0-3 ii libpmem1 1.13.1-1.1+b1 ii libpng16-16t64 1.6.48-1+deb13u3 ii librdmacm1t64 56.1-1 ii libsasl2-2 2.1.28+dfsg1-9 ii libseccomp2 2.6.0-2 ii libslirp0 4.8.0-1+b1 ii libudev1 257.9-1~deb13u1 ii liburing2 2.9-1 ii libvdeplug2t64 4.0.1-5.1+b1 ii libzstd1 1.5.7+dfsg-1 ii qemu-system-common 1:10.0.7+ds-0+deb13u1+b1 ii qemu-system-data 1:10.0.7+ds-0+deb13u1 ii seabios 1.16.3-2 ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1 Versions of packages qemu-system-x86 recommends: ii ovmf 2025.02-8+deb13u1 ii qemu-block-extra 1:10.0.7+ds-0+deb13u1+b1 ii qemu-system-gui 1:10.0.7+ds-0+deb13u1+b1 ii qemu-system-modules-opengl 1:10.0.7+ds-0+deb13u1+b1 ii qemu-system-modules-spice 1:10.0.7+ds-0+deb13u1+b1 ii qemu-utils 1:10.0.7+ds-0+deb13u1+b1 Versions of packages qemu-system-x86 suggests: pn samba <none> pn vde2 <none> -- no debconf information -- regards, Pawel Kudzia
