[Qemu-devel] [Bug 1819343] Re: Qcow2 image stuck as locked after host crash

2019-03-18 Thread Tim Schuster
Yes, it would be v3, I'll use v4 then, thanks! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1819343 Title: Qcow2 image stuck as locked after host crash Status in QEMU: New Bug description: A

[Qemu-devel] [Bug 1819343] Re: Qcow2 image stuck as locked after host crash

2019-03-18 Thread Tim Schuster
Hi, I used both the standard qemu package from the archlinux repositories as well as one I compiled myself with a few patches on top to improve audio performance. According to my logs, the compiled version used 2.28-4, I don't know what archlinux compiles them against. 2.28-5 is currently deploye

[Qemu-devel] [Bug 1819343] [NEW] Qcow2 image stuck as locked after host crash

2019-03-10 Thread Tim Schuster
Public bug reported: After a host crash, the qcow2 image of the VM, stored on a remote NFS share, has become inaccessible. Libvirt/QEMU reports that 'failed to get "write" lock\nIs another process using the image [/path/nfs/image.qcow2]?'. No process is accessing the image from either host or the