From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com, qemu-block@nongnu.org, kchamart@redhat.com,
eblake@redhat.com, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v7 2/3] qemu-img: Document --force-share / -U
Date: Fri, 9 Feb 2018 13:29:14 +0800 [thread overview]
Message-ID: <20180209052915.12855-3-famz@redhat.com> (raw)
In-Reply-To: <20180209052915.12855-1-famz@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
qemu-img.texi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/qemu-img.texi b/qemu-img.texi
index 60a0e080c6..8a26400adb 100644
--- a/qemu-img.texi
+++ b/qemu-img.texi
@@ -86,6 +86,14 @@ exclusive with the @var{-O} parameters. It is currently required to also use
the @var{-n} parameter to skip image creation. This restriction may be relaxed
in a future release.
+@item --force-share (-U)
+If specified, @code{qemu-img} will open the image in shared mode, allowing
+other QEMU processes to open it in write mode. For example, this can be used to
+get the image information (with 'info' subcommand) when the image is used by a
+running guest. Note that this could produce inconsistent results because of
+concurrent metadata changes, etc. This option is only allowed when opening
+images in read-only mode.
+
@item --backing-chain
will enumerate information about backing files in a disk image chain. Refer
below for further description.
--
2.14.3
next prev parent reply other threads:[~2018-02-09 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 5:29 [Qemu-devel] [PATCH v7 0/3] qemu-img: Document --force-share / -U Fam Zheng
2018-02-09 5:29 ` [Qemu-devel] [PATCH v7 1/3] qemu-img.texi: Clean up parameter list Fam Zheng
2018-02-09 5:29 ` Fam Zheng [this message]
2018-02-09 5:29 ` [Qemu-devel] [PATCH v7 3/3] docs: Document share-rw property more thoroughly Fam Zheng
2018-02-09 10:14 ` [Qemu-devel] [PATCH v7 0/3] qemu-img: Document --force-share / -U Stefan Hajnoczi
2018-02-09 13:58 ` Kashyap Chamarthy
2018-02-09 14:47 ` Kevin Wolf
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=20180209052915.12855-3-famz@redhat.com \
--to=famz@redhat.com \
--cc=eblake@redhat.com \
--cc=kchamart@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).