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 deployed on the system. The system is an up-to-date archlinux. I've unmounted and mounted the NFS during my recovery attempts, this should have released any possible lock that was being held, though since the host with qemu crashed and restarted this was more snakeoil than actually trying to fix things. fuser and lsof on the NFS host and QEMU host both showed no process holding a lock on the file. -- 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: 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 network share side. There is no obvious way in qemu-img to force unlocking the file or repair the image (attempting a qemu-img check with -r all results in qemu-img complaining about the lock and being unable to do force-share=on on anything but readonly images). I'm currently attempting to fix this by converting the image via 'qemu-img convert -U -f qcow2 -O qcow2 image.qcow2 image_2.gcow2', though this will likely take some time. Using QEMU 3.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1819343/+subscriptions
