summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/device/1287
blob: 749eb1dfdd66e856774e009aaedf9f0eee2e7685 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
device: 0.799
graphic: 0.686
other: 0.638
instruction: 0.638
network: 0.457
semantic: 0.423
boot: 0.354
mistranslation: 0.329
socket: 0.275
vnc: 0.219
assembly: 0.109
KVM: 0.044

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.