What will cause the validation of a vMotion migration to fail?
A. A virtual machine configured for CPU affinity
B. A virtual machine configured with a local .vswp file
C. A virtual machine configured to use NUMA
D. A virtual machine configured with a shared Raw-Device Mapped disk
Correct Answer: A
Explanation/Reference:
Explanation:
The CPU affinity setting for a virtual machine is used to manage which CPUs on the host the VM can run on. This can help in distributing load between the host CPUs. However, when a VM is configured with a CPU affinity, the validation check performed by the vMotion process will fail.
When performing a VMotion migration the following compatibility warning is displayed:
Unable to migrate from <source server> to <destination server>: Virtual machine has CPU and/or memory affinities configured, preventing VMotion.
To work around the issue you must ensure that there is no CPU affinity configured for the virtual machine. To check the CPU affinity:
Log in to the VirtualCenter as an administrator from the Virtual Infrastructure client.
Right-click on the Virtual Machine.
Click Edit Settings.
Click the Resources tab.
Click the Advanced CPU option.
Check the Scheduling Affinity Section to see if affinity has been set. If affinity has been configured, select the No Affinity radio button to remove the affinity configuration so that you are able to migrate the virtual machine.
To remove the affinity settings in vCenter Server 4.1x and 5.0x, remove the string in Clear the string to remove affinity settings.
Incorrect Answers:
B: A virtual machine configured with a local .vswp file would not cause the vMotion validation to fail. Therefore, this answer is incorrect.
C: A virtual machine configured to use NUMA would not cause the vMotion validation to fail. Therefore, this answer is incorrect.
D: A virtual machine configured with a shared Raw-Device Mapped disk would not cause the vMotion validation to fail. Therefore, this answer is incorrect.
References:
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003842
Explanation/Reference:
Explanation:
The CPU affinity setting for a virtual machine is used to manage which CPUs on the host the VM can run on. This can help in distributing load between the host CPUs. However, when a VM is configured with a CPU affinity, the validation check performed by the vMotion process will fail.
When performing a VMotion migration the following compatibility warning is displayed:
Unable to migrate from <source server> to <destination server>: Virtual machine has CPU and/or memory affinities configured, preventing VMotion.
To work around the issue you must ensure that there is no CPU affinity configured for the virtual machine. To check the CPU affinity:
Log in to the VirtualCenter as an administrator from the Virtual Infrastructure client.
Right-click on the Virtual Machine.
Click Edit Settings.
Click the Resources tab.
Click the Advanced CPU option.
Check the Scheduling Affinity Section to see if affinity has been set. If affinity has been configured, select the No Affinity radio button to remove the affinity configuration so that you are able to migrate the virtual machine.
To remove the affinity settings in vCenter Server 4.1x and 5.0x, remove the string in Clear the string to remove affinity settings.
Incorrect Answers:
B: A virtual machine configured with a local .vswp file would not cause the vMotion validation to fail. Therefore, this answer is incorrect.
C: A virtual machine configured to use NUMA would not cause the vMotion validation to fail. Therefore, this answer is incorrect.
D: A virtual machine configured with a shared Raw-Device Mapped disk would not cause the vMotion validation to fail. Therefore, this answer is incorrect.
References:
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003842