docs: Document watchdog action=dump slightly more

With watchdog action=dump the actual watchdog action is set to pause and
the daemon then proceeds to dump the process.  After that the domain is
resumed.  That was the case since the feature was added.  However the
resuming of the domain might be unexpected, especially when compared to
HW watchdog, which will never run the guest from the point where it got
interrupted.

Document the pre-existing behaviour, since any change might be
unexpected as well.  Change of behaviour would require new options like
dump+reset, dump+pause, etc.  That option is still possible, but
orthogonal to this change.

Resolves: https://issues.redhat.com/browse/RHEL-753
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
This commit is contained in:
Martin Kletzander 2024-10-11 10:31:43 +02:00
parent 37800af9a4
commit 50cc7a0d9d

View File

@ -7914,7 +7914,8 @@ southbridge, which is used with the q35 machine type. :since:`Since 9.1.0`
- 'poweroff' - forcefully power off the guest
- 'pause' - pause the guest
- 'none' - do nothing
- 'dump' - automatically dump the guest :since:`Since 0.8.7`
- 'dump' - automatically dump the guest, beware that after the
dump the guest will be resumed :since:`Since 0.8.7`
- 'inject-nmi' - inject a non-maskable interrupt into the guest
:since:`Since 1.2.17`