diff options
| author | Wenchao Xia <wenchaoqemu@gmail.com> | 2014-06-18 08:43:45 +0200 |
|---|---|---|
| committer | Luiz Capitulino <lcapitulino@redhat.com> | 2014-06-23 11:12:27 -0400 |
| commit | 5a2d2cbd8850db7c03d1333d6c29aab6e3bc75ad (patch) | |
| tree | 48133597437af77e32a5e9a4d27eb5fb96565bc3 /docs | |
| parent | a5ee7bd454ab484022e05537cfcb256e3d6dc90e (diff) | |
| download | qemu-5a2d2cbd8850db7c03d1333d6c29aab6e3bc75ad.zip qemu-5a2d2cbd8850db7c03d1333d6c29aab6e3bc75ad.tar.gz qemu-5a2d2cbd8850db7c03d1333d6c29aab6e3bc75ad.tar.bz2 | |
qapi event: convert BLOCK_IO_ERROR and BLOCK_JOB_ERROR
Signed-off-by: Wenchao Xia <wenchaoqemu@gmail.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/qmp/qmp-events.txt | 47 |
1 files changed, 0 insertions, 47 deletions
diff --git a/docs/qmp/qmp-events.txt b/docs/qmp/qmp-events.txt index d97b389..56bd145 100644 --- a/docs/qmp/qmp-events.txt +++ b/docs/qmp/qmp-events.txt @@ -50,31 +50,6 @@ Example: "size": 65536 }, "timestamp": { "seconds": 1378126126, "microseconds": 966463 } } -BLOCK_IO_ERROR --------------- - -Emitted when a disk I/O error occurs. - -Data: - -- "device": device name (json-string) -- "operation": I/O operation (json-string, "read" or "write") -- "action": action that has been taken, it's one of the following (json-string): - "ignore": error has been ignored - "report": error has been reported to the device - "stop": the VM is going to stop because of the error - -Example: - -{ "event": "BLOCK_IO_ERROR", - "data": { "device": "ide0-hd1", - "operation": "write", - "action": "stop" }, - "timestamp": { "seconds": 1265044230, "microseconds": 450486 } } - -Note: If action is "stop", a STOP event will eventually follow the -BLOCK_IO_ERROR event. - BLOCK_JOB_CANCELLED ------------------- @@ -128,28 +103,6 @@ Example: "speed": 0 }, "timestamp": { "seconds": 1267061043, "microseconds": 959568 } } -BLOCK_JOB_ERROR ---------------- - -Emitted when a block job encounters an error. - -Data: - -- "device": device name (json-string) -- "operation": I/O operation (json-string, "read" or "write") -- "action": action that has been taken, it's one of the following (json-string): - "ignore": error has been ignored, the job may fail later - "report": error will be reported and the job canceled - "stop": error caused job to be paused - -Example: - -{ "event": "BLOCK_JOB_ERROR", - "data": { "device": "ide0-hd1", - "operation": "write", - "action": "stop" }, - "timestamp": { "seconds": 1265044230, "microseconds": 450486 } } - BLOCK_JOB_READY --------------- |