Merge pull request #5729 from Malet/patch-2

Improve vmware-iso disk_type_id documentation
This commit is contained in:
Matthew Hooker 2018-01-31 12:46:33 -08:00 committed by GitHub
commit ed1057518f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 4 deletions

View File

@ -110,10 +110,16 @@ builder.
- `disk_type_id` (string) - The type of VMware virtual disk to create. The - `disk_type_id` (string) - The type of VMware virtual disk to create. The
default is "1", which corresponds to a growable virtual disk split in 2GB default is "1", which corresponds to a growable virtual disk split in 2GB
files. For ESXi, this defaults to "zeroedthick". This option is for files. For ESXi, this defaults to "zeroedthick". This option is for
advanced usage. For more information, please consult the [Virtual Disk advanced usage. For ESXi the available options are: `zeroedthick`, `eagerzeroedthick`, `thin`, `rdm:dev`, `rdmp:dev`, `2gbsparse`. For desktop VMware clients:
Manager User's Guide](https://www.vmware.com/pdf/VirtualDiskManager.pdf)
for desktop VMware clients. For ESXi, refer to the proper ESXi Type ID | Description
documentation. --- | ---
`0` | Growable virtual disk contained in a single file (monolithic sparse).
`1` | Growable virtual disk split into 2GB files (split sparse).
`2` | Preallocated virtual disk contained in a single file (monolithic flat).
`3` | Preallocated virtual disk split into 2GB files (split flat).
`4` | Preallocated virtual disk compatible with ESX server (VMFS flat).
`5` | Compressed disk optimized for streaming.
* `disable_vnc` (boolean) - Whether to create a VNC connection or not. * `disable_vnc` (boolean) - Whether to create a VNC connection or not.
A `boot_command` cannot be used when this is `false`. Defaults to `false`. A `boot_command` cannot be used when this is `false`. Defaults to `false`.