On Thu, Feb 25, 2010 at 12:13:04PM -0300, Luiz Capitulino wrote:
>
> It's emitted whenever the watchdog device's timer expires. The action
> taken is provided in the 'data' member.
>
> Signed-off-by: Luiz Capitulino <lcapitul...@redhat.com>
> ---
> QMP/qmp-events.txt | 19 +++++++++++++++++++
> hw/watchdog.c | 17 +++++++++++++++++
> monitor.c | 3 +++
> monitor.h | 1 +
> 4 files changed, 40 insertions(+), 0 deletions(-)
>
> diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
> index 72920f6..a94e9b4 100644
> --- a/QMP/qmp-events.txt
> +++ b/QMP/qmp-events.txt
> @@ -169,3 +169,22 @@ Example:
> "client": { "family": "ipv4", "service": "46089",
> "host": "127.0.0.1", "sasl_username": "luiz" } },
> "timestamp": { "seconds": 1263475302, "microseconds": 150772 } }
> +
> +WATCHDOG
> +--------
> +
> +Emitted when the watchdog device's timer is expired.
> +
> +Data:
> +
> +- "action": Action that has been taken, it's one of the following
> (json-string):
> + "reset", "shutdown", "poweroff", "pause", "debug", or "none"
> +
> +Example:
> +
> +{ "event": "WATCHDOG",
> + "data": { "action": "reset" },
> + "timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
> +
> +Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is
> +followed respectively by the RESET, SHUTDOWN, or STOP events.
Ok, this should be sufficient for libvirt's needs
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
