From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, kchamart@redhat.com,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2] qemu-img: Document --force-share / -U
Date: Fri, 8 Dec 2017 12:47:48 +0100 [thread overview]
Message-ID: <20171208114748.GA4217@localhost.localdomain> (raw)
In-Reply-To: <20171208095412.GC23880@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Am 08.12.2017 um 10:54 hat Stefan Hajnoczi geschrieben:
> On Fri, Dec 08, 2017 at 09:44:56AM +0800, Fam Zheng wrote:
> > +@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,
> > +etc.
>
> The documentation isn't clear on whether read-write is supported or just
> read-only.
>
> Also, should it be declared a legacy option right away to discourage
> use in new software?
I don't think this is a legacy option. As long you know what you're
doing, using it is fine.
Kevin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-12-08 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 1:44 [Qemu-devel] [PATCH v2] qemu-img: Document --force-share / -U Fam Zheng
2017-12-08 9:54 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-12-08 11:47 ` Kevin Wolf [this message]
2017-12-11 9:30 ` Fam Zheng
2017-12-11 9:05 ` [Qemu-devel] " Kashyap Chamarthy
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=20171208114748.GA4217@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=famz@redhat.com \
--cc=kchamart@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).