qemu-kvm: terminating on signal 15 from pid 75757 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 76046 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 76135 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 76242 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 79735 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 83257 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 83923 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 84764 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 88233 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 91724 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 94324 (/usr/bin/python3)
qemu-kvm: -drive file=/cache/fedora-35_yum_cache,media=disk,if=virtio,format=raw,id=yumcache,snapshot=off: Failed to get "write" lock
Is another process using the image [/cache/fedora-35_yum_cache]?
qemu-kvm: terminating on signal 15 from pid 94783 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 96443 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 96690 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 102999 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 103109 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 106606 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 110128 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 110805 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 111659 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 115127 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 118636 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 121223 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 123592 (/usr/bin/python3)
qemu-kvm: terminating on signal 15 from pid 126577 (/usr/bin/python3)