diff options
| author | Luiz Capitulino <lcapitulino@redhat.com> | 2012-05-08 14:24:48 -0300 |
|---|---|---|
| committer | Michael Roth <mdroth@linux.vnet.ibm.com> | 2012-05-15 09:15:16 -0500 |
| commit | 432d29db0db9d08fe34a57b8c03af20c9f759d77 (patch) | |
| tree | cddff91567de08eb6371400be5fecdfeb3428371 /block/blkverify.c | |
| parent | c6fcc10ab31d22e93eb169c451025ac9636ec84b (diff) | |
qemu-ga: guest-suspend-ram: don't emit a success response
Today, qemu-ga may not be able to emit a success response when
guest-suspend-ram completes. This happens because the VM may
suspend before qemu-ga is able to emit a response.
This semantic is a bit confusing, as it's not clear for clients if
they should wait for a response or how they should check for success.
This commit solves that problem by changing guest-suspend-ram to
never emit a success response and suggests in the documentation
what clients should do to check for success.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Diffstat (limited to 'block/blkverify.c')
0 files changed, 0 insertions, 0 deletions