qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, stefanha@redhat.com, kchamart@redhat.com,
	Kevin Wolf <kwolf@redhat.com>,
	eblake@redhat.com, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v6 2/2] qemu-img: Document --force-share / -U
Date: Tue, 30 Jan 2018 14:34:33 +0800	[thread overview]
Message-ID: <20180130063433.11605-3-famz@redhat.com> (raw)
In-Reply-To: <20180130063433.11605-1-famz@redhat.com>

Signed-off-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
 qemu-img.texi | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/qemu-img.texi b/qemu-img.texi
index 60a0e080c6..ec7e2f5d1e 100644
--- a/qemu-img.texi
+++ b/qemu-img.texi
@@ -86,6 +86,13 @@ 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
+concurrent writers. 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

  parent reply	other threads:[~2018-01-30  6:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  6:34 [Qemu-devel] [PATCH v6 0/2] qemu-img: Document --force-share / -U Fam Zheng
2018-01-30  6:34 ` [Qemu-devel] [PATCH v6 1/2] qemu-img.texi: Clean up parameter list Fam Zheng
2018-01-30 13:50   ` Eric Blake
2018-01-30  6:34 ` Fam Zheng [this message]
2018-01-30 12:14   ` [Qemu-devel] [PATCH v6 2/2] qemu-img: Document --force-share / -U Stefan Hajnoczi
2018-01-30 13:52   ` Eric Blake
2018-01-30 14:23   ` Eric Blake
2018-01-30 14:34     ` Kashyap Chamarthy
2018-01-30 16:38     ` Kevin Wolf
2018-01-31 14:12       ` Stefan Hajnoczi
2018-01-31 14:22         ` Kevin Wolf
2018-02-01 11:44           ` Stefan Hajnoczi
2018-02-09  3:29             ` Fam Zheng
2018-02-09  3:31             ` Fam Zheng

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=20180130063433.11605-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).