diff options
| author | Luiz Capitulino <lcapitulino@redhat.com> | 2012-08-09 11:27:30 -0300 |
|---|---|---|
| committer | Luiz Capitulino <lcapitulino@redhat.com> | 2012-08-13 16:10:18 -0300 |
| commit | 17c8660b0b2be17d389e2ffd5681d535cc0d8912 (patch) | |
| tree | 1877932eddf8841012d90a621124844d694c07a6 /QMP | |
| parent | 1405819637f53ed8021067eb3ea52e32bef2870b (diff) | |
qmp: emit the WAKEUP event when the guest is put to run
Today, the WAKEUP event is emitted when a wakeup _request_ is made.
This could be the system_wakeup command, for example.
A better semantic would be to emit the event when the guest is
already running, as that's what matters in the end. This commit does
that change.
In theory, this could break compatibility. In practice, it shouldn't
happen though, as clients shouldn't rely on timing characteristics of
the events. That is, a client relying that the guest is not running
when the event arrives may break if the event arrives after the guest
is already running.
This commit also adds the missing documentation for the WAKEUP event.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'QMP')
| -rw-r--r-- | QMP/qmp-events.txt | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt index 9ba7079589..10f69d1906 100644 --- a/QMP/qmp-events.txt +++ b/QMP/qmp-events.txt @@ -264,6 +264,19 @@ Example: }} +WAKEUP +------ + +Emitted when the guest has woken up from S3 and is running. + +Data: None. + +Example: + +{ "event": "WATCHDOG", + "timestamp": { "seconds": 1344522075, "microseconds": 745528 } } + + WATCHDOG -------- |