Am 12.12.2017 um 01:51 hat Fam Zheng geschrieben:
> Signed-off-by: Fam Zheng <f...@redhat.com>
>
> ---
>
> v4: "images". [Kevin]
>
> 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..d93501f94f 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.
>
> +@item --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,
Each time you read a text, you find something new...
s/result/results/
> +etc. This option is only allowed when opening images in read-only mode.
> +
Thanks, fixed the above and applied the patch to block-next.
Kevin
