From 3e4c5a6261770bced301b5e74233e7866166ea5b Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Sun, 1 Jun 2025 21:35:14 +0200 Subject: clean up repository --- .../issues_text/target_missing/host_missing/accel_missing/1357 | 9 --------- 1 file changed, 9 deletions(-) delete mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/1357 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1357') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1357 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1357 deleted file mode 100644 index dbfcf7530..000000000 --- a/gitlab/issues_text/target_missing/host_missing/accel_missing/1357 +++ /dev/null @@ -1,9 +0,0 @@ -qemu-img should generate VMDK with an EOS marker when `has_marker` flag enabled -Additional information: -I generate a empty volume with capacity 1G and try to deploy it as a part of OVF. This would fail. - -But when I append an EOS marker to that VMDK, which is actually a zeroed sector, the deployed procedure succeeded. - -This case merely happened if VMDK has data, since `qemu-img` always write at least one grain(64 KB). So the padding part will be recognized as EOS marker. - -I have written a temporary patch for this and it works fine for me. I'm glad to send it for review. -- cgit 1.4.1