diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
| commit | dee4dcba78baf712cab403d47d9db319ab7f95d6 (patch) | |
| tree | 418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/deepseek-r1:14b/output/files/1287 | |
| parent | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff) | |
| download | emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip | |
restructure results
Diffstat (limited to 'results/classifier/deepseek-r1:14b/output/files/1287')
| -rw-r--r-- | results/classifier/deepseek-r1:14b/output/files/1287 | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/results/classifier/deepseek-r1:14b/output/files/1287 b/results/classifier/deepseek-r1:14b/output/files/1287 new file mode 100644 index 00000000..2c7a2cdd --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/files/1287 @@ -0,0 +1,11 @@ + +qemu-img info foo.qcow2 tries to get write lock +Description of problem: +When trying to run qemu-img info on an image which is used by QEMU qemu-img tries to acquire a write lock. Ideally this would not attempt to acquire a write lock and let qemu-img info succeed. +``` +[jelle@t14s][/tmp]%qemu-img info /var/tmp/cockpit-qr_j3e_m.qcow2 +qemu-img: Could not open '/var/tmp/cockpit-qr_j3e_m.qcow2': Failed to get shared "write" lock +Is another process using the image [/var/tmp/cockpit-qr_j3e_m.qcow2]? +``` +Steps to reproduce: +1. Run qemu-img on an image used by a QEMU process. |