6.7

A Yes status indicates that the snapshot files for the virtual machine should be consolidated, and that
the virtual machine's Tasks and Events tab shows a configuration problem. A No status indicates
that the files are OK.
2 To consolidate the files, right-click the virtual machine and select Snapshots > Consolidate.
3 Check the Needs Consolidation column to verify that the task succeeded.
If the task succeeded, a Not Required value appears in the Needs Consolidation column.
4 If the task failed, check the event log for failed conditions, such as running out of disk space.
5 Correct the error, and retry the consolidation task.
The configuration problem is resolved, and the Needs Consolidation value is Not Required.
Enhanced vMotion Compatibility as a Virtual Machine
Attribute
Cluster-level EVC ensures CPU compatibility between hosts in a cluster, so that you can seamlessly
migrate virtual machines within the EVC cluster. In vSphere 6.7, you can also enable, disable, or change
the EVC mode at the virtual machine level. The per-VM EVC feature facilitates the migration of the virtual
machine beyond the cluster and across vCenter Server systems and datacenters that have different
processors.
The EVC mode of a virtual machine is independent from the EVC mode defined at the cluster level. The
cluster-based EVC mode limits the CPU features a host exposes to virtual machines. The per-VM EVC
mode determines the set of host CPU features that a virtual machine requires in order to power on and
migrate.
By default, when you power on a newly created virtual machine, it inherits the feature set of its parent
EVC cluster or host. However, you can change the EVC mode for each virtual machine separately. You
can raise or lower the EVC mode of a virtual machine. Lowering the EVC mode increases the CPU
compatability of the virtual machine. You can also use the API calls to customize the EVC mode further.
Cluster-based EVC and Per-VM EVC
There are several differences between the way the EVC feature works at the host cluster level and at the
virtual machine level.
n
Unlike cluster-based EVC, you can change the per-VM EVC mode only when the virtual machine is
powered off.
n
With cluster-based EVC, when you migrate a virtual machine out of the EVC cluster, a power cycle
resets the EVC mode that the virtual machine has. With Per-VM EVC, the EVC mode becomes an
attribute of the virtual machine. A power cycle does not affect the compatibility of the virtual machine
with different processors.
n
When you configure EVC at the virtual machine level, the per-VM EVC mode overrides cluster-based
EVC. If you do not configure per-VM EVC, when you power on the virtual machine, it inherits the EVC
mode of its parent EVC cluster or host.
vSphere Virtual Machine Administration
VMware, Inc. 254