
Installation Guide
88 VMware, Inc.
VMotion
For you to use VMotion, all blades in a VirtualCenter farm need access to the same
logical unit number (LUN) on a SAN. Consequently, the VMFS volumes that contain
the virtual machine virtual disk (.vmdk) files must be on a shared SAN accessible by ESX
Server.
Core Dump Partition
ESX Server core dump partitions must be on a controller visible to the virtual machines
(VMkernel). We recommend that you create ESX Server core dump partitions either on
a local SCSI drive or on the SAN.
We recommend that you create a separate core dump partition for each ESX server on
Intel blades. For example, you can use a separate LUN for each ESX Server machine that
contains both its core dump partition and the swap file, discussed in the following
section.
Swap File
ESX Server swap partitions must be on a controller visible to the virtual machines
(VMkernel). We recommend that you create ESX Server swap partitions on a local SCSI
drive, or on the SAN.
Purchase enough physical memory to prevent virtual machine swapping from being a
significant performance issue.
Depending on the number of blades and your swap usage, you may choose to allocate
a dedicated LUN for swap files. Multiple swap files from multiple ESX servers can
reside on this dedicated LUN. Do not store any other kind of file (virtual machine .vmdk
files, checkpoint files, and so on) on this LUN.
Use a unique name for each blade server swap file, such as <ip>-1.vswp. Although you
can have a total of eight swap files for each ESX Server machine, you can select only one
swap file through the VMware Management Interface.
N
OTE VMotion is not supported for virtual machines hosted on local storage. The virtual
machine must reside on a shared SAN.
Comentarios a estos manuales