From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH] qmp: Documentation for BLOCK_IMAGE_CORRUPTED
Date: Mon, 2 Sep 2013 15:01:24 +0200 [thread overview]
Message-ID: <1378126884-9544-1-git-send-email-mreitz@redhat.com> (raw)
Add an appropriate entry describing this event and its parameters into
qmp-events.txt.
Signed-off-by: Max Reitz <mreitz@redhat.com>
---
Follow-up to:
- Add metadata overlap checks (series, v5); particularly patch 2
(qcow2: Metadata overlap checks)
---
QMP/qmp-events.txt | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
index 39b6016..6ff74d6 100644
--- a/QMP/qmp-events.txt
+++ b/QMP/qmp-events.txt
@@ -478,3 +478,25 @@ Example:
{ "event": "GUEST_PANICKED",
"data": { "action": "pause" } }
+
+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 } }
--
1.8.3.1
next reply other threads:[~2013-09-02 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 13:01 Max Reitz [this message]
2013-09-03 13:39 ` [Qemu-devel] [PATCH] qmp: Documentation for BLOCK_IMAGE_CORRUPTED Eric Blake
2013-09-03 13:51 ` Max Reitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1378126884-9544-1-git-send-email-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).