Which two statements are true about High Priority vMotion requests in vSphere 5.x?

Which two statements are true about High Priority vMotion requests in vSphere 5.x? (Choose two.)

A.
Migrations always proceed regardless of whether or not resources have been successfully reserved.

B.
Migrations do not proceed if resources are not successfully reserved.

C.
vCenter Server attempts to reserve resources on both the source and destination hosts to be shared among all concurrent migrations with vMotion.

D.
vCenter Server attempts to reserve resources on both the source and destination hosts for each individual High Priority migration with vMotion.

9 Comments on “Which two statements are true about High Priority vMotion requests in vSphere 5.x?

  1. Francesco says:

    Correct answer are not B and C?
    I think that A is not correct because when High Priority is set the migration does not proceed if resource are not successfully reserved am I wrong?

  2. Roman Dronov says:

    Regards to http://www.vmwarehub.com/Migration-with-vmotion.html

    High Priority – vCenter Server reserves resources on both the source and destination hosts to maintain virtual machine availability during the migration. High priority migrations do not proceed if resources are unavailable.

    Low Priority – vCenter Server does not reserve resources on the source and destination hosts to maintain availability during the migration. Low priority migrations always proceed. However, the virtual machine might become briefly unavailable if host resources are unavailable during the migration.

    So, B. & C.

    1. Jon says:

      That information is incorrect. From VMware documentation: http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.vm_admin.doc_50/GUID-0542FCAA-209A-4296-8AA4-0A51C13A6233.html

      High Priority-
      On hosts running ESX/ESXi version 4.1 or later, vCenter Server attempts to reserve resources on both the source and destination hosts to be shared among all concurrent migrations with vMotion. vCenter Server grants a larger share of host CPU resources to high priority migrations than to standard priority migrations. !!!Migrations always proceed regardless of the resources that have been reserved.!!!

      On hosts running ESX/ESXi version 4.0 or earlier, vCenter Server attempts to reserve a fixed amount of resources on both the source and destination hosts for each individual migration. High priority migrations do not proceed if resources are unavailable.

      1. Ron says:

        Francesco is correct–Answers are A and C. Appropriate link is

        http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc_50%2FGUID-0542FCAA-209A-4296-8AA4-0A51C13A6233.html

        Note that the question refers to vSphere 5.x so the first paragraph in the High Priority section pertains:

        ***On hosts running ESX/ESXi version 4.1 or later, vCenter Server attempts to reserve resources on both the source and destination hosts to be shared among all concurrent migrations with vMotion.*** vCenter Server grants a larger share of host CPU resources to high priority migrations than to standard priority migrations. ***Migrations always proceed regardless of the resources that have been reserved.***


Leave a Reply

Your email address will not be published. Required fields are marked *