blob: 0c230ac8e073a5c59933555268cc310b81169316 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
device: 0.896
other: 0.884
vnc: 0.807
network: 0.800
semantic: 0.614
graphic: 0.600
PID: 0.587
debug: 0.538
performance: 0.474
boot: 0.413
files: 0.351
permissions: 0.290
socket: 0.286
KVM: 0.006
Failed to get write lock on qcow2 image from a sigkilled vm
Additional information:
That feature will solve an issue i have with qemu that i muself created
by sending a `kill -9` to a qemu VM after it stopped accepting vnc connections.
I can't use the same qcow2 image currently. Maybe a reboot will fix it, but i did
check `lslocks` and there was no lock on it there.
|