Information Technology Reference
In-Depth Information
7.
Select the priority that the vMotion migration needs to proceed with.
In vSphere 5.5, this setting controls the share of reserved resources allocated for
migrations with vMotion. Migrations marked as Reserve CPU For Optimal vMotion
Performance receive a reserved share of CPU resources compared to migrations marked
as Perform With Available CPU Resources. Migrations will proceed regardless of the
resources reserved. This behavior is different than in earlier versions; see the sidebar
“Migration Priority in Earlier Versions of vSphere.” Generally, you will select Reserve
CPU… (Recommended). Click Next to continue.
Migration Priority in Earlier Versions of vSphere
h e behavior of the High Priority / Reserved CPU and Standard Priority / Non-Reserved settings
for vMotion changed in vSphere 4.1; this behavior carries forward to vSphere 5.5 as described in
the text. For vSphere 4, however, the behavior of these options is diff erent. For vSphere 4, high-
priority migrations do not proceed if resources are unavailable to be reserved for the migration,
whereas standard priority migrations will proceed. However, standard priority migrations might
proceed more slowly and might even fail to complete if enough resources are not available.
8.
Review the settings, and click Finish if all the information is correct.
If there are any errors, use the Back button or the hyperlinks on the left to go back and
correct the errors.
9.
The VM should start to migrate. Often, the process will pause at about 14 percent in the
progress dialog box and then again at 65 percent.
The 14 percent pause occurs while the hosts in question establish communications and
gather the information for the pages in memory to be migrated; the 65 percent pause
occurs when the source VM is quiesced and the dirty memory pages are fetched from the
source host, as shown in Figure 12.8.
Figure 12.8
h e Recent Tasks
pane of the Web
Client shows the
progress of the
vMotion operation.
