diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
| commit | 3e4c5a6261770bced301b5e74233e7866166ea5b (patch) | |
| tree | 9379fddaba693ef8a045da06efee8529baa5f6f4 /gitlab/issues_text/target_missing/host_missing/accel_missing/1357 | |
| parent | e5634e2806195bee44407853c4bf8776f7abfa4f (diff) | |
| download | qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.tar.gz qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.zip | |
clean up repository
Diffstat (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1357')
| -rw-r--r-- | gitlab/issues_text/target_missing/host_missing/accel_missing/1357 | 9 |
1 files changed, 0 insertions, 9 deletions
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. |