diff options
| author | Fam Zheng <famz@redhat.com> | 2013-08-19 18:54:27 +0800 |
|---|---|---|
| committer | Stefan Hajnoczi <stefanha@redhat.com> | 2013-08-22 15:35:58 +0200 |
| commit | daac8fdc68c5f0118ce24fcac5873ddaa0d0c9f9 (patch) | |
| tree | 1b4378de3f68df91ef147b60c362bef1e65dfbc2 /arch_init.c | |
| parent | f6b61e54bdd5b9ef46837c15547e1819b3bb4f37 (diff) | |
| download | hqemu-daac8fdc68c5f0118ce24fcac5873ddaa0d0c9f9.zip hqemu-daac8fdc68c5f0118ce24fcac5873ddaa0d0c9f9.tar.gz | |
vmdk: support vmfsSparse files
VMware ESX hosts use a variant of the VMDK3 format, identified by the
vmfsSparse create type ad the VMFSSPARSE extent type.
It has 16 KB grain tables (L2) and a variable-size grain directory (L1).
In addition, the grain size is always 512, but that is not a problem
because it is included in the header.
The format of the extents is documented in the VMDK spec. The format
of the descriptor file is not documented precisely, but it can be
found at http://kb.vmware.com/kb/10026353 (Recreating a missing virtual
machine disk (VMDK) descriptor file for delta disks).
With these patches, vmfsSparse files only work if opened through the
descriptor file. Data files without descriptor files, as far as I
could understand, are not supported by ESX.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
--
v2: Rebase to patch 01.
Change le64_to_cpu to le32_to_cpu.
Rename vmdk_open_vmdk3 to vmdk_open_vmfs_sparse, which represents the
current usage of this format.
Signed-off-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'arch_init.c')
0 files changed, 0 insertions, 0 deletions
