summary refs log tree commit diff stats
path: root/gitlab/issues_text/target_missing/host_missing/accel_missing/2039
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-05-30 16:52:07 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-05-30 16:52:17 +0200
commit9260319e7411ff8281700a532caa436f40120ec4 (patch)
tree2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues_text/target_missing/host_missing/accel_missing/2039
parent225caa38269323af1bfc2daadff5ec8bd930747f (diff)
downloadqemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.tar.gz
qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.zip
gitlab scraper: download in toml and text format
Diffstat (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/2039')
-rw-r--r--gitlab/issues_text/target_missing/host_missing/accel_missing/203911
1 files changed, 11 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2039 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2039
new file mode 100644
index 000000000..bd38d9705
--- /dev/null
+++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2039
@@ -0,0 +1,11 @@
+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:
+