From 0ca0b0d5f8a87dbc6daa5095771d036d0e6dc5b4 Mon Sep 17 00:00:00 2001 From: Max Reitz Date: Tue, 3 Sep 2013 15:49:39 +0200 Subject: [PATCH] qmp: Documentation for BLOCK_IMAGE_CORRUPTED Add an appropriate entry describing this event and its parameters into qmp-events.txt. Signed-off-by: Max Reitz Reviewed-by: Eric Blake Reviewed-by: Kevin Wolf Signed-off-by: Stefan Hajnoczi --- QMP/qmp-events.txt | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt index 39b6016460..4b24ec900d 100644 --- a/QMP/qmp-events.txt +++ b/QMP/qmp-events.txt @@ -18,6 +18,28 @@ Example: "data": { "actual": 944766976 }, "timestamp": { "seconds": 1267020223, "microseconds": 435656 } } +BLOCK_IMAGE_CORRUPTED +--------------------- + +Emitted when a disk image is being marked corrupt. + +Data: + +- "device": Device name (json-string) +- "msg": Informative message (e.g., reason for the corruption) (json-string) +- "offset": If the corruption resulted from an image access, this is the access + offset into the image (json-int) +- "size": If the corruption resulted from an image access, this is the access + size (json-int) + +Example: + +{ "event": "BLOCK_IMAGE_CORRUPTED", + "data": { "device": "ide0-hd0", + "msg": "Prevented active L1 table overwrite", "offset": 196608, + "size": 65536 }, + "timestamp": { "seconds": 1378126126, "microseconds": 966463 } } + BLOCK_IO_ERROR --------------