Description of problem:
For libvirt watchdog action=dump, when it is triggered, the guest will pause and libvirt coredumps the guest, which is fine.  However libvirt then resumes the guest which is definitely not fine (it should restart it).

Version-Release number of selected component (if applicable):
libvirt-9.0.0-3.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start vm with watchdog device:

1. virsh dumpxml rhel --xpath //watchdog
   <watchdog model="i6300esb" action="dump">
     <address type="pci" domain="0x0000" bus="0x10" slot="0x01" function="0x0"/>
   </watchdog>

1. virsh start rhel
   Domain 'rhel' started

2. Trigger the watchdog in the vm and wait for 30s, vm will pause and generate the dump file, then libvirt will resume the vm:

1.  echo 1 > /dev/watchdog
   [   71.910336] watchdog: watchdog0: watchdog did not stop!
   (check the status on vm, after 30s, it will pause for several seconds, then resume. No reset.)

Watch the domstate on the host, after 30s, the vm will be pause, and then resume to running status:

1. watch virsh domstate rhel

Check there is coredump file created on the host:

1. ll /var/lib/libvirt/qemu/dump
   total 2088772
   rw------. 1 root root 2138900771 Feb  7 21:06 3-rhel-2023-02-07-21:06:48

Actual results:
For libvirt watchdog action=dump, when it is triggered, the guest will pause and libvirt coredumps the guest, which is fine.  However libvirt then resumes the guest which is definitely not fine (it should restart it).

Expected results:
After coredump, libvirt should reset the vm

Additional info: