A vSphere administrator is attempting to migrate a virtual machine, but the progress bar for the migration remains at 10%.
Which issue could be preventing the vMotion migration?
A. A networking problem between the source and destination hosts exists at the physical layer.
B. The virtual machine is not on shared storage visible to the source and destination hosts.
C. The vMotion migration priority for this migration was set to High.
D. The vMotion network is saturated.
Correct Answer: A
Explanation/Reference:
Explanation:
When you perform a vMotion migration of a virtual machine (VM), vMotion first performs validation checks to check for issues that could be preventing a vMotion migration such as a locally attached device. The validation checks take up the first 10% of the vMotion progress bar.
In this question, the progress bar reached 10%. This means that the validation checks have been completed. When the progress bar stops at 10%, it is because the actual vMotion migration is unable to proceed. This of often due to physical networking problems on the vMotion network between the source and destination hosts.
Incorrect Answers:
B: If the virtual machine was not on shared storage visible to the source and destination hosts, the validation checks would fail and the progress bar would not reach 10%. Therefore, this answer is incorrect.
C: 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. Therefore, this answer is incorrect.
D: Each operation, such as vMotion migration or cloning a virtual machine, is assigned a resource cost. Each type of resource, such as host, datastore, or network, has a maximum cost that it can support at any one time. Any new migration or provisioning operation that would cause a resource to exceed its maximum cost does not proceed immediately, but is queued until other operations complete and release resources. If the vMotion network was saturated, it would be because there are current operations in progress. In this case, the vMotion of the VM in this question would be queued. The progress bar would not reach 10% until the vMotion operation had started. Therefore, this answer is incorrect.
References:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003734
http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUID-25EA5833-03B5-4EDD-A167-87578B8009B3.html