What were you trying to do that didn't work?

What is the impact of this issue to you?

Please provide the package NVR for which the bug is seen:

How reproducible is this bug?:

Steps to reproduce

1. run qemu virtual machine with -snapshot parameter

   /usr/libexec/qemu-kvm -name guest=snapshot,debug-threads=on -S -object {"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-snapshot/master-key.aes"} -machine pc-i440fx-rhel7.6.0,usb=off,dump-guest-core=off,memory-backend=pc.ram -accel tcg -cpu qemu64 -m size=8388608k -object {"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592} -overcommit mem-lock=off -smp 4,sockets=4,cores=1,threads=1 -uuid cd9c94c0-98c0-40f0-99d6-d00e19741c32 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=31,server=on,wait=off -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device {"driver":"piix3-usb-uhci","id":"usb","bus":"pci.0","addr":"0x1.0x2"} -blockdev {"driver":"file","filename":"/tmp/test-cirros.raw","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-1-format","read-only":false,"driver":"raw","file":"libvirt-1-storage"} -device {"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x4","drive":"libvirt-1-format","id":"virtio-disk0","bootindex":1} -device {"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"} -audiodev {"id":"audio1","driver":"none"} -vnc 0.0.0.0:4101,audiodev=audio1 -k en-us -device {"driver":"cirrus-vga","id":"video0","bus":"pci.0","addr":"0x2"} -device {"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.0","addr":"0x5"} -snapshot -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on 

1.  use ps command to get the qemu-kvm virtual machine process id(vmid)
2.  use `lsof -p vmid` command to obtain files opened by the virtual machine process
3.  check if there is an open vl.xxxxx(deleted) file
4.  we testing in rhel 9.5 (qemu 9.0) and 9.0 (qemu 6.2), it was found that the tmp file (vl.xxxxx) was not created. The content written by the virtual machine was directly written to the image, causing the -snapshot function to not work properly.

Expected results

The vl.xxxxx file is created normally, and all writes to the virtual machine are written to this tmp file.

Actual results

The vl.xxxxx file is not created, and all writes to the virtual machine are written to volume.