diff options
author | Sam Eiderman | 2019-06-20 11:10:55 +0200 |
---|---|---|
committer | Max Reitz | 2019-06-24 15:53:02 +0200 |
commit | 940a2cd5d2eede3c81b83712c55cc6d3c5e6c463 (patch) | |
tree | a5842b1bf82c9115bcffde3a4e33a032f7ffc38d /tests/qemu-iotests/072 | |
parent | iotest 134: test cluster-misaligned encrypted write (diff) | |
download | qemu-940a2cd5d2eede3c81b83712c55cc6d3c5e6c463.tar.gz qemu-940a2cd5d2eede3c81b83712c55cc6d3c5e6c463.tar.xz qemu-940a2cd5d2eede3c81b83712c55cc6d3c5e6c463.zip |
vmdk: Fix comment regarding max l1_size coverage
Commit b0651b8c246d ("vmdk: Move l1_size check into vmdk_add_extent")
extended the l1_size check from VMDK4 to VMDK3 but did not update the
default coverage in the moved comment.
The previous vmdk4 calculation:
(512 * 1024 * 1024) * 512(l2 entries) * 65536(grain) = 16PB
The added vmdk3 calculation:
(512 * 1024 * 1024) * 4096(l2 entries) * 512(grain) = 1PB
Adding the calculation of vmdk3 to the comment.
In any case, VMware does not offer virtual disks more than 2TB for
vmdk4/vmdk3 or 64TB for the new undocumented seSparse format which is
not implemented yet in qemu.
Reviewed-by: Karl Heubaum <karl.heubaum@oracle.com>
Reviewed-by: Eyal Moscovici <eyal.moscovici@oracle.com>
Reviewed-by: Liran Alon <liran.alon@oracle.com>
Reviewed-by: Arbel Moshe <arbel.moshe@oracle.com>
Signed-off-by: Sam Eiderman <shmuel.eiderman@oracle.com>
Message-id: 20190620091057.47441-2-shmuel.eiderman@oracle.com
Reviewed-by: yuchenlin <yuchenlin@synology.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/072')
0 files changed, 0 insertions, 0 deletions