# Disk DescriptorFile
version=1
CID=fffffffe
parentCID=ffffffff
createType="monolithicSparse"
# Extent description
RW 18432000 SPARSE "test.vmdk"
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "3"
ddb.geometry.cylinders = "16383"
ddb.geometry.heads = "16"
ddb.geometry.sectors = "63"
ddb.adapterType = "ide"
|
"monolithicSparse"
This type uses an embedded descriptor
Avoid absolute paths with embedded descriptors!
Extract it from test.vmdk like this:
dsfo.exe test.vmdk 512 800 descriptor.txt
In case you need to edit it - inject it again like this:
dsfi.exe test.vmdk 512 800 descriptor.txt
Required files:
"test.vmdk"
|
# Disk DescriptorFile
version=1
CID=fffffffe
parentCID=ffffffff
createType="monolithicFlat"
# Extent description
RW 27648000 FLAT "test-flat.vmdk" 0
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "3"
ddb.geometry.cylinders = "16383"
ddb.geometry.heads = "16"
ddb.geometry.sectors = "63"
ddb.adapterType = "ide"
|
"monolithicFlat"
Required files:
"test.vmdk"
"test-flat.vmdk"
This type can be redefined as VMFS
so it is directly usable with ESX.
Instead of assigning a regular *-flat.vmdk
you can also assign *.img files like used with Starwind iSCSI
- or assign dd-images created with Linux
|
# Disk DescriptorFile
version=1
CID=fffffffe
parentCID=ffffffff
createType="twoGbMaxExtentSparse"
# Extent description
RW 4192256 SPARSE "test-s001.vmdk"
RW 4192256 SPARSE "test-s002.vmdk"
RW 4192256 SPARSE "test-s003.vmdk"
RW 1759232 SPARSE "test-s004.vmdk"
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "3"
ddb.geometry.cylinders = "14222"
ddb.geometry.heads = "16"
ddb.geometry.sectors = "63"
ddb.adapterType = "ide"
|
"twoGbMaxExtentSparse"
Required files:
"test.vmdk"
"test-s001.vmdk"
"test-s002.vmdk"
"test-s003.vmdk"
"test-s004.vmdk" |
# Disk DescriptorFile
version=1
CID=fffffffe
parentCID=ffffffff
createType="twoGbMaxExtentFlat"
# Extent description
RW 3072000 FLAT "test-f001.vmdk" 0
RW 3072000 FLAT "test-f002.vmdk" 0
RW 3072000 FLAT "test-f003.vmdk" 0
RW 3072000 FLAT "test-f004.vmdk" 0
RW 3072000 FLAT "test-f005.vmdk" 0
RW 3072000 FLAT "test-f006.vmdk" 0
RW 3072000 FLAT "test-f007.vmdk" 0
RW 3072000 FLAT "test-f008.vmdk" 0
# The Disk Data Base
#DDBddb.virtualHWVersion = "3"
ddb.geometry.cylinders = "16383"
ddb.geometry.heads = "16"
ddb.geometry.sectors = "63"
ddb.adapterType = "ide"
|
"twoGbMaxExtentFlat"
Required files:
"test.vmdk"
"test-f001.vmdk"
"test-f002.vmdk"
"test-f003.vmdk"
"test-f004.vmdk"
"test-f005.vmdk"
"test-f006.vmdk"
"test-f007.vmdk"
"test-f008.vmdk" |
# Disk DescriptorFile
version=1
CID=54bcc741
parentCID=ffffffff
createType="fullDevice"
# Extent description
RW 156296385 FLAT "\\.\PhysicalDrive0" 0
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "6"
ddb.geometry.cylinders = "9729"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.geometry.biosCylinders = "9729"
ddb.geometry.biosHeads = "255"
ddb.geometry.biosSectors = "63"
ddb.adapterType = "lsilogic"
ddb.toolsVersion = "0"
|
"fullDevice"
Required files:
"test.vmdk"
PhysicalDrive0
VMserver 2 can handle this format but it no longer can create
it.
VMserver 1 can handle and create this format.
|
# Disk DescriptorFile
version=1
CID=526c949e
parentCID=ffffffff
createType="partitionedDevice"
# Extent description
RW 63 FLAT "test-pt.vmdk" 0
RW 24579387 FLAT "\\.\PhysicalDrive0" 63
RW 131716935 ZERO
RW 5103 ZERO
# The Disk Data Base
#DDB
ddb.adapterType = "ide"
ddb.geometry.biosSectors = "63"
ddb.geometry.biosHeads = "255"
ddb.geometry.biosCylinders = "1024"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "16"
ddb.geometry.cylinders = "16383"
ddb.virtualHWVersion = "4"
ddb.toolsVersion = "0"
|
"partitionedDevice"
Required files:
"test.vmdk"
"test-pt.vmdk"
PhysicalDrive0
"test-pt.vmdk" is a copy of the MBR of the original
disk.
VMserver 2 can handle this format but it no longer can create
it.
VMserver 1 can handle and create this format.
|
# Disk DescriptorFile
version=1
CID=7341dd22
parentCID=ffffffff
createType="vmfs"
# Extent description
RW 16777216 VMFS "test-flat.vmdk"
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "4"
ddb.toolsVersion = "0"
ddb.geometry.cylinders = "1044"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"
|
"vmfs"
Required files:
"test.vmdk"
"test-flat.vmdk"
this type can be redefined as monolithicFlat
so it can be easily be used with Workstation.
Workstation can handle this format.
|
# Disk DescriptorFile
version=1
CID=33333333
parentCID=22222222
createType="vmfsSparse"
parentFileNameHint="test.vmdk"
# Extent description
RW 146800640 VMFSSPARSE "test-000001-delta.vmdk"
# The Disk Data Base
#DDB
ddb.toolsVersion = "7202" |
"vmfsSparse"
Required files:
"test-000001-delta.vmdk"
"test-000001.vmdk"
used for snapshots on ESX.
Workstation can handle this format but it can not create it. |
# Disk Descriptor file
version=1
CID=e323f28b
parentCID=ffffffff
CreateType="custom"
# Extent Description
RDONLY 63 ZERO
RDONLY 156296322 V2I "virtual-pc-diskformat.v2i"
RDONLY 32130 ZERO
# The disk database
# DDB
ddb.virtualHWVersion = "4"
ddb.geometry.cylinders = "9731"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "buslogic"
|
"custom"
used for v2i disk format
note the usage of "RDONLY"
Required files:
"test.vmdk"
"virtual-pc-diskformat.v2i"
|
# Disk DescriptorFile
version=1
CID=fa4e4198
parentCID=77ae5c02
createType="twoGbMaxExtentSparse"
parentFileNameHint="test.vmdk"
# Extent description
RW 4192256 SPARSE "test-000001-s001.vmdk"
RW 4192256 SPARSE "test-000001-s002.vmdk"
RW 4192256 SPARSE "test-000001-s003.vmdk"
RW 4192256 SPARSE "test-000001-s004.vmdk"
RW 8192 SPARSE "test-000001-s005.vmdk"
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "6"
ddb.toolsVersion = "0" |
"twoGbMaxExtentSparse-snapshot"
Required files:
"test-000001.vmdk"
"test-000001-s001.vmdk"
"test-000001-s002.vmdk"
"test-000001-s003.vmdk"
"test-000001-s004.vmdk"
"test-000001-s005.vmdk"
|
# Disk DescriptorFile
version=1
CID=e1649e95
parentCID=e1649e95
createType="monolithicSparse"
parentFileNameHint="test.vmdk"
# Extent description
RW 16777216 SPARSE "test-000001.vmdk"
# The Disk Data Base
#DDB
|
"monolithicSparse-snapshot"
Required files:
"test-000001.vmdk"
This type uses an embedded descriptor
Avoid absolute paths with embedded descriptors!
You can extract the descriptor from this type of snapshots
the same way as mentioned with "monolithicSparse"
|
# Disk Descriptor file
version=1
CID=e323f28b
parentCID=ffffffff
CreateType="custom"
# Extent Description
RDONLY 63 ZERO
RDONLY 156296322 V2I "virtual-pc-diskformat.v2i"
RDONLY 32130 ZERO
# The disk database
# DDB
ddb.virtualHWVersion = "4"
ddb.geometry.cylinders = "9731"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "buslogic"
|
"custom"
used for v2i disk format
or other third-party images
note the usage of "RDONLY"
Required files:
"test.vmdk"
"virtual-pc-diskformat.v2i"
|
# Disk Descriptor file
version=1
CID=e323f28b
parentCID=ffffffff
CreateType="custom"
# Extent Description
RDONLY 63 ZERO
RDONLY 160521417 SPF "C_VOL-b001.spf"
RDONLY 2048 ZERO
# The disk database
# DDB
ddb.virtualHWVersion = "4"
ddb.geometry.cylinders = "9992"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "buslogic"
|
"custom"
used by
StorageCraft ShadowProtect backup
Required files:
the *.spf image itself and a vmdk descriptor like this one |
# Disk DescriptorFile
version=1
CID=3a7b3c99
parentCID=e323f28b
createType="twoGbMaxExtentSparse"
parentFileNameHint="drive-0.vmdk.rdonly"
# Extent description
RW 4192256 SPARSE "drive-0-s001.vmdk"
RW 4192256 SPARSE "drive-0-s002.vmdk"
....
....
RW 4192256 SPARSE "drive-0-s037.vmdk"
RW 4192256 SPARSE "drive-0-s038.vmdk"
RW 1217800 SPARSE "drive-0-s039.vmdk"
# The Disk Data Base
#DDB
ddb.encoding = "windows-1252"
ddb.geometry.biosCylinders = "9992"
ddb.geometry.biosSectors = "63"
ddb.geometry.biosHeads = "255"
|
this is a snapshot for the Stoarge Craft Shadow protect from
above |
#
Disk DescriptorFile
version=1
encoding="windows-1252"
CID=f19b298e
parentCID=ffffffff
createType="streamOptimized"
# Extent description
RW 16777216 SPARSE "test.vmdk"
# The Disk Data Base
#DDB
ddb.geometry.biosSectors = "63"
ddb.geometry.biosHeads = "255"
ddb.geometry.biosCylinders = "1044"
ddb.adapterType = "lsilogic"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "255"
ddb.geometry.cylinders = "1044"
ddb.uuid = "60 00 C2 9f 9b b0 9d 17-15 6c 54 9c 40 8d 33
71"
ddb.virtualHWVersion = "7"
ddb.toolsVersion = "0" |
"streamOptimized"
this type is used along with an ovf file
which can be regarded as an "obscured" version of
the regular vmx-file - this time in xml-format.
This type uses an embedded descriptor
Avoid absolute paths with embedded descriptors!
Extract it from test.vmdk like this:
dsfo.exe test.vmdk 512 800 descriptor.txt
In case you need to edit it - inject it again like this:
dsfi.exe test.vmdk 512 800 descriptor.txt
|
# Disk DescriptorFile
version=1
CID=c56639e1
parentCID=ffffffff
createType="vmfsPassthroughRawDeviceMap"
# Extent description
RW 251658240 VMFSRDM "EX2_1-rdmp.vmdk"
# The Disk Data Base
#DDB
ddb.toolsVersion = "6310"
ddb.adapterType = "lsilogic"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "255"
ddb.geometry.cylinders = "15665"
ddb.virtualHWVersion = "4" |
"vmfsPassthroughRawDeviceMap"
|