diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/files/1287 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/files/1287')
| -rw-r--r-- | results/classifier/gemma3:12b/files/1287 | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/files/1287 b/results/classifier/gemma3:12b/files/1287 new file mode 100644 index 000000000..2c7a2cddd --- /dev/null +++ b/results/classifier/gemma3:12b/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. |