Bug 1763519
| Summary: | qcow2 corruption | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Sebek <dasebek> | ||||
| Component: | qemu | Assignee: | Fedora Virtualization Maintainers <virt-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 31 | CC: | amit, berrange, cfergeau, cody6730, crobinso, dwmw2, itamar, mmuehlfe, pbonzini, rjones, virt-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | qemu-4.1.0-5.fc31 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-11-02 02:28:00 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Related bug report: https://bugs.launchpad.net/qemu/+bug/1846427 Thanks for finding that upstream bug. I've subscribed to it so let's see what fix they come up with. It sounds (from the upstream bug) as if it's something pretty serious. Should we unpush this version of qemu for a while? I'm doing a build with 69f47505ee66afaa513305de0c1895a224e52c45 reverted, which kwolf suggested FEDORA-2019-9a30568ecf has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-9a30568ecf qemu-4.1.0-5.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-9a30568ecf qemu-4.1.0-5.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. I'm having what seems to be the same problem, as referenced in this bug. https://bugzilla.redhat.com/show_bug.cgi?id=1768541 The problem still exists in qemu-4.1.0-5.fc31. It is impossible to overstate the seriousness of this bug. The upgrade to Fedora 31 has caused the unrecoverable loss of every virtual machine that existed on this machine. |
Created attachment 1627499 [details] sudo qemu-img check mi-rev-win10.qcow2 &> qemu-img_check.txt Description of problem: About a week ago I created a Windows 10 VM using virt-manager. Everything worked OK until I started the VM today (it was started only a few times before). Some file system corruption was detected and automatically fixed by the guest Windows 10 OS during its bootup. Now some of the components of the guest Windows operating system do not work. Checking the qcow2 virtual disk image using the "qemu-img check" command returns a bunch of errors. Version-Release number of selected component (if applicable): [david@dsebek-pc KVM]$ qemu-kvm --version QEMU emulator version 4.1.0 (qemu-4.1.0-2.fc31) Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers [david@dsebek-pc KVM]$ virt-manager --version 2.2.1 How reproducible: I haven't tried to reproduce it. Steps to Reproduce: 1. Start creating a new Windows 10 virtual machine using virt-manager. 2. Create a QCOW2 disk image. 3. Select UEFI instead of BIOS. 4. Use VirtIO SCSI as a disk controller. 5. Set 'discard' option to 'unmap' in VM's disk section. 6. Finish creating the VM, install the guest Windows 10 Pro operating system. 7. Use the VM for a few hours, turn it on and off a few times. 8. A file system corruption will occur on the guest OS, "qemu-img check" will return errors. Actual results: Corruption of qcow2 disk image was experienced. Expected results: No corruption of qcow2 disk image is expected. Additional info: Host machine uses Fedora 31, Luks, Ext4, fstrim about once in a few days.