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

Start a transient tdx domain, the reboot it, then the domain disappears

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

# rpm -q libvirt qemu-kvm kernel
libvirt-11.10.0-2.el9.x86_64
qemu-kvm-10.1.0-10.el9.x86_64
kernel-5.14.0-644.7224_2182954267.el9.x86_64

How reproducible is this bug?:100%

Steps to reproduce

1. A tdx domain xml is as below:
<os firmware='efi'>
…
<firmware>
      <feature enabled='yes' name='enrolled-keys'/>
      <feature enabled='yes' name='secure-boot'/>
 </firmware>
<loader>/usr/share/edk2/ovmf/OVMF.inteltdx[.secboot.fd|http://ovmf.inteltdx.secboot.fd/]</loader>
<nvram template='/usr/share/edk2/ovmf/OVMF_VARS.secboot.fd'>/var/lib/libvirt/qemu/nvram/vm1_VARS.fd</nvram>
…
</os>
…
<memory unit='KiB'>8388608</memory>
<currentMemory unit='KiB'>8388608</currentMemory>
<memoryBacking>
    <access mode='private'/>
</memoryBacking>
<cpu mode='host-passthrough' />
…
<devices>
…
<memballoon model='none'/>
…
</devices>
<launchSecurity type='tdx'>
    <policy>0x10000000</policy>
    <quoteGenerationService path='/var/run/tdx-qgs/qgs.socket'/>
</launchSecurity>
...

2. Start a transient tdx domain:

# virsh create vm1.xml
Domain 'vm1' created from vm1.xml

3. After the domain boots up, reboot it via virsh reboot:

# virsh reboot vm1
Domain 'vm1' is being rebooted

4. Use virsh list to check the domain

# virsh list --all
 Id   Name   State
--------------------

5. check whether there is domain process:

# ps -ef | grep qemu-kvm | grep -v grep

Expected results

The virsh list cmd could find the tdx domain, and there exists domain process in host.

Actual results

The virsh list cmd could not find the tdx domain, and there is no domain process in host.