Resource Management Guide : Advanced Resource Management : Advanced Attributes and What They Do : Setting Advanced Virtual Machine Attributes

Setting Advanced Virtual Machine Attributes
This section first steps you through setting advanced attributes for a virtual machine, and then lists a small number of attributes you might want to set under certain circumstances.
To set advanced attributes for a virtual machine
Click Options and click Advanced.
Click the Configuration Parameters button.
In the dialog box that is displayed, click Add Row to enter a new parameter and its value.
You can set the following advanced attributes for virtual machines:
Maximum amount of memory that can be reclaimed from the selected virtual machine by ballooning, in megabytes (MB). If the ESX Server host needs to reclaim additional memory, it is forced to swap. Swapping is less desirable than ballooning.
This boolean value defaults to True. If you set it to False for a virtual machine, memory sharing is turned off.
Specifies whether the virtual machine’s swap files should persist or be deleted when the virtual machine is powered off. By default, the system creates the swap file for a virtual machine when the virtual machine is powered on, and deletes the swap file when the virtual machine is powered off.
VMFS directory where the virtual machine's swap file is located. Defaults to the virtual machine's working directory, that is, the VMFS directory that contains its configuration file.
Filename for the virtual machine's swap file. By default, the system generates a unique name when it creates the swap file.
Sets the address to ping to determine if a host is isolated from the network. If this option is not specified, the default gateway of the console network is used. This default gateway has to be some reliable address that is known to be available, so that the host can determine if it is isolated from the network.
If this is set, VMware HA will first try to fail over hosts to the host specified by this option. This is useful if you want to utilize one host as a spare failover host, but is not usually recommended, because VMware HA tries to utilize all available spare capacity among all hosts in the cluster.
If the specified host does not have enough spare capacity, VMware HA tries to fail over the virtual machine to any other host in the cluster that has enough capacity.