6.5.1

4 Next to swap le location, click Edit.
5 Select where to store the swap le.
Option Description
Virtual machine directory
Stores the swap le in the same directory as the virtual machine
conguration le.
Datastore specified by host
Stores the swap le in the location specied in the host conguration.
If the swap le cannot be stored on the datastore that the host species, the
swap le is stored in the same folder as the virtual machine.
6 Click OK.
Delete Swap Files
If a host fails, and that host had running virtual machines that were using swap les, those swap les
continue to exist and consume many gigabytes of disk space. You can delete the swap les to eliminate this
problem.
Procedure
1 Restart the virtual machine that was on the host that failed.
2 Stop the virtual machine.
The swap le for the virtual machine is deleted.
Sharing Memory Across Virtual Machines
Many ESXi workloads present opportunities for sharing memory across virtual machines (as well as within
a single virtual machine).
ESXi memory sharing runs as a background activity that scans for sharing opportunities over time. The
amount of memory saved varies over time. For a fairly constant workload, the amount generally increases
slowly until all sharing opportunities are exploited.
To determine the eectiveness of memory sharing for a given workload, try running the workload, and use
resxtop or esxtop to observe the actual savings. Find the information in the PSHARE eld of the interactive
mode in the Memory page.
Use the Mem.ShareScanTime and Mem.ShareScanGHz advanced seings to control the rate at which the system
scans memory to identify opportunities for sharing memory.
You can also congure sharing for individual virtual machines by seing the sched.mem.pshare.enable
option.
Due to security concerns, inter-virtual machine transparent page sharing is disabled by default and page
sharing is being restricted to intra-virtual machine memory sharing. This means page sharing does not occur
across virtual machines and only occurs inside of a virtual machine. The concept of salting has been
introduced to help address concerns system administrators may have over the security implications of
transparent page sharing. Salting can be used to allow more granular management of the virtual machines
participating in transparent page sharing than was previously possible. With the new salting seings,
virtual machines can share pages only if the salt value and contents of the pages are identical. A new host
cong option Mem.ShareForceSalting can be congured to enable or disable salting.
See Chapter 15, “Advanced Aributes,” on page 115 for information on how to set advanced options.
vSphere Resource Management
40 VMware, Inc.