From: Jan Heidbrink <1721788@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1721788] Re: Failed to get shared "write" lock with 'qemu-img info'
Date: Fri, 23 Apr 2021 13:43:25 -0000 [thread overview]
Message-ID: <161918540561.31655.16551856642503337164.malone@soybean.canonical.com> (raw)
In-Reply-To: 150729895903.22243.5921581973131047310.malonedeb@gac.canonical.com
Ah ok, I think this bug can be closed then.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1721788
Title:
Failed to get shared "write" lock with 'qemu-img info'
Status in QEMU:
Fix Released
Bug description:
When running 'qemu-img info test.qcow2' while test.qcow2 is currently
used by a Qemu process, I get the error
qemu-img: Could not open 'test.qcow2': Failed to get shared "write"
lock.
Why does displaying information about a disk image need a write lock
for the file?
Steps to reproduce:
qemu-img create -f qcow2 test.qcow2 10M
qemu-system-x86_64 -nographic -drive file=test.qcow2
qemu-img info test.qcow2
The above was tested with Qemu version 2.10.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1721788/+subscriptions
next prev parent reply other threads:[~2021-04-23 13:52 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
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 [this message]
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=161918540561.31655.16551856642503337164.malone@soybean.canonical.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.