blob: 5b1df8f08276b00c2f79152e2ec0a0a64b441a02 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
id = 1357
title = "qemu-img should generate VMDK with an EOS marker when `has_marker` flag enabled"
state = "opened"
created_at = "2022-12-07T12:06:59.834Z"
closed_at = "n/a"
labels = ["Storage"]
url = "https://gitlab.com/qemu-project/qemu/-/issues/1357"
host-os = "n/a"
host-arch = "n/a"
qemu-version = "n/a"
guest-os = "n/a"
guest-arch = "n/a"
description = "n/a"
reproduce = "n/a"
additional = """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."""
|