>From what I see, the fix would be to use --force-share when invoking `qemu-img create -b <backing-image-path> -f qcow2 <imgpath>` as of qemu 2.10 which is currently not the case:
https://github.com/juju/juju/blob/juju-2.5.2/container/kvm/wrappedcmds.go#L474-L485 out, err := params.runCmd( "qemu-img", "create", "-b", backingPath, "-f", "qcow2", imgPath, fmt.Sprintf("%dG", params.RootDisk)) https://git.qemu.org/?p=qemu.git;a=commit;h=335e9937844449a3fc172dd5e64549ad7d5ad1c2 git --no-pager tag --contains=335e9937844449a3fc172dd5e64549ad7d5ad1c2 | grep -v rc v2.10.0 v2.10.1 v2.10.2 v2.11.0 v2.11.1 v2.11.2 v2.12.0 v2.12.1 v3.0.0 v3.1.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816170 Title: KVM instances fail at creation with: Failed to get shared "write" lock Is another process using the image? To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1816170/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
