diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:24:58 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:27:06 +0000 |
| commit | 33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch) | |
| tree | 406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/1721788 | |
| parent | adedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff) | |
| download | qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip | |
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1721788')
| -rw-r--r-- | results/scraper/launchpad-without-comments/1721788 | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1721788 b/results/scraper/launchpad-without-comments/1721788 new file mode 100644 index 000000000..63fecba7f --- /dev/null +++ b/results/scraper/launchpad-without-comments/1721788 @@ -0,0 +1,16 @@ +Failed to get shared "write" lock with 'qemu-img info' + +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 \ No newline at end of file |