The preferences file contains options that control the Provisioning and Cloning capability operation.
This file is stored by default in the following location, where [VSC_home] is your VSC for VMware vSphere installation directory:
[VSC_home]\etc\kamino\kaminoprefs.xml The preferences file contains the following options.
Note: Line breaks have been placed in some of the option types and values so that the table will fit on the page. If you are setting up a preferences file, do not include the line breaks.
Type Value Description
log4j.config.file log4j.
properties
Filename of the log configuration file. This file contains parameters that determine the level of events that are written to the log file. The log configuration filename can be changed here in the kaminoprefs file, and the new configuration file must be stored in [VSC_home]\etc\kamino. default.create.copy
NvramFile
false Clones the VM BIOS file (.nvram). This option is necessary when using Citrix Provisioning server because the boot device order and PXE settings need to be cloned as well.
default.create.
exportToAllVm KernelNics
false Determines if the storage controller exports file will contain all IP addresses of all VMkernel ports.
For example, if a dedicated storage network with IP address 192.168.0/24 and a second VMkernel network 10.10/16 on a public network for ISO mounting have this value set to true, the newly created datastores are exported to VMkernel addresses on both networks. The default behavior of false restricts the export to only the VMkernel addresses that share the same network as the IP address of the controller used to mount the datastore.
default.create.
volume.option.
fractional_reserve
0 Fractional reserve allows the system administrator to reduce the amount of guaranteed available reserve space. By doing this, the administrator can tune the amount of space guaranteed to be
available for LUN overwrites based on application requirements and make better use of available
Type Value Description
volume space. It is adjustable between 0 and 100%
of the size of the LUN.
default.create.
volume.option.
no_atime_update
on Disables updating of access time when files are read. Leave on for better performance in a heavy read traffic environment.
default.create.
volume.option.nosnap
on Disables Snapshot copies for new FlexClone volumes.
default.create.
volume.option.sis
true Enables deduplication on new volumes.
default.create.
volume.snapreserve
0 Sets the snapshot reserve size for new volumes to the specified percentage.
default.create.
volume.lunSpaceBuffer
5 Sets 5 GB as the amount of additional capacity in a volume that contains a LUN-based datastore.
default.create.
volume.useThickFor VolThatContainLun
false Space reservation override for thin LUN-based datastore.
Default volume space reservation for a thin LUN is thin. Setting this option to true results in a thin LUN in a thick volume when a thin LUN is chosen.
Note: Applies only to Datastore Create. It has no effect on Datastore Clone.
default.create.
volume.useThin ForVolClone
true Space reservation override for volumes created using FlexClone technology.
Datastores will all be thin FlexClones unless this option is set to false.
Note: Applies only to Datastore Clone. It has no effect on Datastore Create.
default.destroy.
checkPossible CrossMount
true If an administrator mounts a volume for use as a datastore to an ESX host using a different IP address or volume path than what was used to mount the volume to other ESX hosts, there is a potential for the Destroy feature to incorrectly report which VMs are present on the datastore.
This is because the datastore UUID is generated by
Type Value Description
the ESX host based on the IP address and volume path.
checkPossibleCrossMount addresses this issue and therefore should be left set to true. The only time this should be set to false is if the Destroy window stays in the "Loading..." state for an extended period of time and there is no chance of the issue described above.
default.destroy.
destroyParent IfLastClone
true When last FlexClone volume is destroyed, the golden volume is destroyed.
default.destroy.
onlyOffline
false By default, the Destroy feature takes offline and destroys the volume that was mounted as a datastore. Setting this option to true leaves the volume intact, just offline.
default.destroy.
onlyUnreg
false By default, the Destroy feature chooses the most efficient VM cleanup method. Setting this option to true forces it to unregister the VM in all cases.
default.destroy.
destroyVolIfLastLun
false When last LUN is removed, volume is not destroyed. Setting this option to true causes volume to be destroyed when last LUN is removed.
default.mount.
volume.mountUsing Hostname
Not present If true, hostname is retrieved by reverse name lookup using system-configured lookup service.
Hostname is then used to mount the datastore.
default.restrict.
nfs.mount.networks
None By default, any matching network between the controller and the ESX VMKernel is used to mount datastores. In some implementations, certain networks should not be used for mounting, even if they contain the required interfaces on both the controller and ESX hosts. This value prevents a network from being used to mount NFS datastores.
The example below tells the Provisioning and Cloning capability to ignore the 192.168.2.0, 10.1.0.0, and 2001:5a0:400:200::0 networks when
Type Value Description
determining the IP address on the controller to use for the next NFS datastore:
<entry key="default.restrict.nfs.
None By default, any matching network between the controller and the ESX VMKernel is used to mount datastores. In some implementations, certain networks should not be used for mounting, even if they contain the required interfaces on both the controller and ESX hosts. This value prevents a network from being used to mount iSCSI datastores. The example below tells the
Provisioning and Cloning capability to ignore the 192.168.2.0, 10.1.0.0, and 2001:5a0:400:200::0 networks when determining the IP address on the controller that will be used for the next iSCSI datastore.
all Any matching network between controller and ESX VMKernel is used to mount NFS datastores.
In some implementations, it is important to fence off the networks that should be used for NFS and those that should be used for iSCSI. This option allows only specified networks to mount NFS datastores. The network specified is that of the VMKernel interface, not an interface on the storage system. The all keyword means that all matching networks between the VMkernels and the storage system interfaces can be used for mounting NFS datastores. You can specify different
networks here to enable mounting across different subnets.
default.allow.iscsi.
mount.networks
all Any matching network between controller and ESX VMKernel is used to map iSCSI datastores.
Type Value Description
In some implementations, it is important to fence off the networks that should be used for NFS and those that should be used for iSCSI. This option allows only the specified networks to map iSCSI-based VMFS datastores. The network specified is that of the VMKernel interface, not an interface on the storage system.
default.create.
igroup.alua
yes Configures the ALUA setting to apply to new iGroups.
default.option.
copythreads
4 Controls number of simultaneous file copies.
Maximum is 16.
default.option.
powerOffThreads
10 Controls number of simultaneous VM power off operations. Maximum is 16.
default.option.
checkAlignment
true Controls whether alignment is checked on the source VM.
default.option.
fallBackToNdmpCopy
true Specifies whether the clone operation should fall back to using NDMP copy if the flex-clone operation begins to copy blocks rather than clone them. This happens when a block has reached the max shared blocks limit.
default.option.
fallBackThreshold
0 Specifies a threshold for copying blocks before falling back to using an NDMP copy. Blocks copied threshold is specified as a percentage. This is used if the
default.option.fallBackToNdmpCopy preference is set to true. For example, setting this value to 20 will fall back to using NDMP copy if 20% of the blocks during the FlexClone operation have been copied. Default behavior is to fall back immediately when any blocks have been copied.
default.option.
controllerValidation Timeout
120 By default, controller validation is cancelled if it takes longer than two minutes to validate a controller. In some large environments, it may be necessary to increase this timeout. The example below tells the Provisioning and Cloning capability
Type Value Description
to wait five minutes (300 seconds) before canceling the validation operation.
<entry key="default.option.
controllerValidationTimeout"
value="300"/>