The qemu 4.1.0 upgrade killed pretty much all my VMs. I had data
corruption (i.e. tar was unable to extract some larger data archives for
testing purposes) in all my Linux VMs and other strange errors. The
Windows VM was killed after I ran "qemu-img check -r all" on the image.
Afterwards Windows wa
I was unable to compile the qemu-git package and I currently have not
time to investigate that. But I updated to 4.1.1. I just started my
Windows 10 VM with that and after a short time of use the image was
corrupted again. Here is my full start parameter set. Maybe there is
something wrong or I sho
The image was fine before upgrading qemu. I rechecked the image after
the first use and it was fine. But after the larger Windows 1903 -> 1909
upgrade done in qemu 4.1.0 the image was damaged. I will try the git
master version of qemu in the coming days and report back.
--
You received this bug n
I tried the ArchLinux package that includes three patches applied to
qemu 4.1 ( see
https://git.archlinux.org/svntogit/packages.git/commit/trunk/PKGBUILD?h=packages/qemu&id=e9707066408de26aa04f8d0ddebe5556aa87e662
). My Windows 10 qcow2 image got corrupted again after a short time of
use. Host file
I have the same (related?) issue and wanted to add my experience with it. I had
3 qemu qcow2 VM running on ArchLinux. I never used snapshots or something like
it. Just normal start&shutdown. 2 of these VMs were also ArchLinux running on
ext4. Both of these VMs had a data corruption inside the qu
