From: Liang Yan <lyan@suse.com>
To: Bug 1721788 <1721788@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1721788] Re: Failed to get shared "write" lock with 'qemu-img info'
Date: Wed, 11 Oct 2017 16:46:40 -0400 [thread overview]
Message-ID: <b10b109e-9a87-bf4e-bc72-eea4c0bcee70@suse.com> (raw)
In-Reply-To: <150730021408.8281.13104272267482208285.malone@wampee.canonical.com>
This does not only affect qemu-img only, it could not make libvirt
"<shareable>" work either when two vms were running with share disk
image. Is there a workaround for this situation?
Best,
Liang
On 10/6/17 10:30 AM, Daniel Berrange wrote:
> I've just noticed, however, that '--force-share' appears totally
> undocumented in both CLI help output and the man page. So that's
> certainly something that should be fixed
>
next prev parent reply other threads:[~2017-10-11 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 14:09 [Qemu-devel] [Bug 1721788] [NEW] Failed to get shared "write" lock with 'qemu-img info' Jan Heidbrink
2017-10-06 14:28 ` [Qemu-devel] [Bug 1721788] " Daniel Berrange
2017-10-06 14:28 ` [Qemu-devel] [Bug 1721788] [NEW] " Eric Blake
2017-10-06 14:30 ` [Qemu-devel] [Bug 1721788] " Daniel Berrange
2017-10-11 20:46 ` Liang Yan [this message]
2021-04-22 5:29 ` Thomas Huth
2021-04-22 8:14 ` Jan Heidbrink
2021-04-22 11:05 ` Max Reitz
2021-04-23 13:43 ` Jan Heidbrink
2022-04-19 14:35 ` Kaitlyn Lew
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=b10b109e-9a87-bf4e-bc72-eea4c0bcee70@suse.com \
--to=lyan@suse.com \
--cc=1721788@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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).