VMware VCENTER SERVER 4.0 - GETTING STARTED UPDATE 1 Specifications Page 115

  • Download
  • Add to my manuals
  • Print
  • Page
    / 146
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 114
Swapfile Location Compatibility
Virtual machine swapfile location affects vMotion compatibility in different ways depending on the version
of ESXi running on the virtual machine's host.
Virtual machines on hosts running ESX Server 3.0.x have a virtual machine swap file located with the virtual
machine configuration file. Virtual machines on these hosts can be migrated with vMotion only if the
destination host can access the VMFS volume where the swap file is located.
You can configure ESX 3.5 or ESXi 3.5 or later hosts to store virtual machine swapfiles in one of two locations:
with the virtual machine configuration file, or on a local swapfile datastore specified for that host. You can also
set individual virtual machines to have a different swapfile location from the default set for their current host.
The location of the virtual machine swapfile affects vMotion compatibility as follows:
n
Migrations between hosts running ESX/ESXi version 3.5 and later: Migrations with vMotion and
migrations of suspended and powered-off virtual machines are allowed.
During a migration with vMotion, if the swapfile location specified on the destination host differs from
the swapfile location specified on the source host, the swapfile is copied to the new location. This can result
in slower migrations with vMotion. If the destination host cannot access the specified swapfile location,
it stores the swapfile with the virtual machine configuration file.
n
Migrations between a host running ESX/ESXi version 3.5 and later and a host running an earlier version
of ESX: Migrations of suspended and powered-off virtual machines are allowed. If the virtual machine is
configured to use a local swapfile datastore, attempting to migrate it to a host that does not support this
configuration produces a warning, but the migration can proceed. When the virtual machine is powered
on again, the swapfile is located with the virtual machine.
Migrations with vMotion are not allowed unless the destination swapfile location is the same as the source
swapfile location. In practice, this means that virtual machine swapfiles must be located with the virtual
machine configuration file.
See the vSphere Client online Help for more information on configuring swapfile policies.
Migrating Virtual Machines with Snapshots
Migration of virtual machines with snapshots is possible if the virtual machine resides on shared storage
accessible to source and destination hosts.
Migrating a virtual machine with snapshots is permitted, regardless of the virtual machine power state, as long
as the virtual machine is being migrated to a new host without moving its configuration file or disks. (The
virtual machine must reside on shared storage accessible to both hosts.)
If the migration involves moving the configuration file or virtual disks, the following additional restrictions
apply:
n
The starting and destination hosts must be running ESX 3.5 or ESXi 3.5 or later.
n
All of the virtual machine files and disks must reside in a single directory, and the migrate operation must
move all the virtual machine files and disks to a single destination directory.
Reverting to a snapshot after migration with vMotion might cause the virtual machine to fail, because the
migration wizard cannot verify the compatibility of the virtual machine state in the snapshot with the
destination host. Failure occurs only if the configuration in the snapshot uses devices or virtual disks that are
not accessible on the current host, or if the snapshot contains an active virtual machine state that was running
on hardware that is incompatible with the current host CPU.
Chapter 12 Migrating Virtual Machines
VMware, Inc. 115
Page view 114
1 2 ... 110 111 112 113 114 115 116 117 118 119 120 ... 145 146

Comments to this Manuals

No comments