diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:07 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:17 +0200 |
| commit | 9260319e7411ff8281700a532caa436f40120ec4 (patch) | |
| tree | 2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues_text/target_missing/host_missing/accel_missing/1357 | |
| parent | 225caa38269323af1bfc2daadff5ec8bd930747f (diff) | |
| download | qemu-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/1357')
| -rw-r--r-- | gitlab/issues_text/target_missing/host_missing/accel_missing/1357 | 9 |
1 files changed, 9 insertions, 0 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 new file mode 100644 index 000000000..dbfcf7530 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/1357 @@ -0,0 +1,9 @@ +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. |