blob: 586813f55a95abb23bc06a0cb1d356754c4b85e7 (
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
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
device: 0.874
performance: 0.866
graphic: 0.850
virtual: 0.795
mistranslation: 0.766
network: 0.745
semantic: 0.741
kernel: 0.695
VMM: 0.692
permissions: 0.675
PID: 0.674
vnc: 0.656
risc-v: 0.655
ppc: 0.636
debug: 0.632
architecture: 0.629
boot: 0.626
register: 0.624
arm: 0.588
peripherals: 0.508
hypervisor: 0.446
socket: 0.433
user-level: 0.397
TCG: 0.369
i386: 0.346
KVM: 0.326
assembly: 0.322
x86: 0.232
files: 0.151
there is no 'write' lock checked when exec `qemu-img check lvqcow2`
Description of problem:
There is a difference between a qcow2 file image and a lvqcow2 img.
'write' lock will be checked when using a normal qcow2-format image (/path/to/img/test.qcow2) to avoid some risky operations. However, when I create a qcow2 img on a lv, there is not any write lock checked when I perform `qemu-img check` on this lvqcow2 even though it was attached to a vm.
Steps to reproduce:
1. create a lvqcow2: `qemu-img create -f qcow2 /path/to/lv xxG`
2. create a vm using this lvqcow2
3. exec `qemu-img check` on this lvqcow2, there is no any perm (such as 'write' lock) check and notifaction even though this lvqcow2 is using in qemu vm.
Additional information:
|