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

  • Download
  • Add to my manuals
  • Print
  • Page
    / 146
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 123
In some cases, where a choice between CPU compatibility or guest operating system features (such as NX/XD)
exists, VMware provides check-box options to configure individual virtual machines through the virtual
machine’s Advanced Settings option. For more control over the visibility of CPU features, you can edit the
virtual machine’s CPU compatibility mask at the bit level.
CAUTION This is an experimental feature. Manual edit of the CPU compatibility masks without the appropriate
documentation and testing might lead to an unsupported configuration.
CPU compatibility masks cannot prevent virtual machines from accessing masked CPU features in all
circumstances. In some circumstances, applications can detect and use masked features even though they are
hidden from the guest operating system. In addition, on any host, applications that use unsupported methods
of detecting CPU features rather than using the CPUID instruction can access masked features. Virtual
machines running applications that use unsupported CPU detection methods might experience stability
problems after migration.
About Migration Compatibility Checks
During migration, the Migrate Virtual Machine wizard checks the destination host for compatibility with the
migrating virtual machine using a number of criteria.
When you select a host, the Compatibility panel at the bottom of the Migrate Virtual Machine wizard displays
information about the compatibility of the selected host or cluster with the virtual machine’s configuration.
If the virtual machine is compatible, the panel displays the message, Validation succeeded. If the virtual
machine is not compatible with either the host’s or cluster’s configured networks or datastores, the
compatibility window can display both warnings and errors:
n
Warning messages do not disable migration. Often the migration is justified and you can continue with
the migration despite the warnings.
n
Errors can disable migration if there are no error-free destination hosts among the selected destination
hosts. In this case, the Next button is disabled.
For clusters, the network and datastore configurations are taken into account when checking compatibility
issues. For hosts, the individual host’s configuration is used. A possible problem might be that vMotion is not
enabled on one or both hosts.
A specific host CPU feature’s effects on compatibility are dependent on whether ESXi exposes or hides them
from virtual machines.
n
Features that are exposed to virtual machines are not compatible when they are mismatched.
n
Features that are not exposed to virtual machines are compatible regardless of mismatches.
Specific items of virtual machine hardware can also cause compatibility issues. For example, a virtual machine
using an enhanced vmxnet virtual NIC cannot be migrated to a host running a version of ESXi that does not
support enhanced vmxnet.
Migrate a Powered-Off or Suspended Virtual Machine in the vSphere
Client
You can use the Migration wizard to migrate a powered-off virtual machine or suspended virtual machine.
Procedure
1 Select the virtual machine that you want to migrate in the inventory.
2 Right-click on the virtual machine and select Migrate from the pop-up menu.
vCenter Server and Host Management
124 VMware, Inc.
Page view 123
1 2 ... 119 120 121 122 123 124 125 126 127 128 129 ... 145 146

Comments to this Manuals

No comments