[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-block] [PATCH v3] qemu-img: Document --force-share / -U
From: |
Fam Zheng |
Subject: |
[Qemu-block] [PATCH v3] qemu-img: Document --force-share / -U |
Date: |
Mon, 11 Dec 2017 17:33:14 +0800 |
Signed-off-by: Fam Zheng <address@hidden>
---
v3: Document that the option is not allowed for read-write. [Stefan]
v2: - "code{qemu-img}". [Kashyap, Eric]
- "etc.." -> "etc.".
---
qemu-img.texi | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/qemu-img.texi b/qemu-img.texi
index fdcf120f36..d85ace73f0 100644
--- a/qemu-img.texi
+++ b/qemu-img.texi
@@ -57,6 +57,15 @@ 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.
address@hidden --force-share (-U)
+
+If specified, @code{qemu-img} will open the image with shared permissions,
+which makes it less likely to conflict with a running guest's permissions due
+to image locking. 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 result because of concurrent metadata changes,
+etc. This option is only allowed when opening image in read-only mode.
+
@item fmt
is the disk image format. It is guessed automatically in most cases. See below
for a description of the supported disk formats.
--
2.14.3
- [Qemu-block] [PATCH v3] qemu-img: Document --force-share / -U,
Fam Zheng <=