A vSphere administrator has a 4 host DRS cluster with plans to grow to 8 hosts. During a vMotion
migration, the following error is displayed:
— Exhibit —
— Exhibit —
What action could be taken to resolve the issue?
A.
Ensure all hosts in the cluster contain only Intel or AMD CPUs
B.
Choose Reset all to Default in the CPU Identification Mask of the VM
C.
Verify and correct the vmkernel port settings for the vMotion network
D.
Configure the DRS Migration Threshold to the most conservative setting
Explanation:
Agree with B
http://www.jjclements.co.uk/2009/09/15/vmware-vmotion-cpu-problem-after-vsphere-upgrade/
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011294
0
0
And this one:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1993
0
0
Reverting to the Default CPU Compatibility Bit Mask
Revert to the default vMotion compatibility constraints by reverting any changes made to the default mask. This can be accomplished by following the appropriate steps for the type of masking that was applied:
– When using per-virtual-machine masks, reset any changed rows to the defaults by clicking Reset All to Default on the CPU Identification Mask dialog box.
– When using global masks: Remove any added tags entered in the vpxd.cfg file and restart the VirtualCenter service.
0
0
Masking or hiding CPU features can make a virtual machine widely available to ESXi hosts for migration. vCenter Server compares the CPU features available to a virtual machine with the CPU features of the destination host to determine whether to allow or disallow migration with vMotion.
https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.hostclient.doc%2FGUID-0779E302-81AE-469D-9F3F-9098B6B52D41.html&resultof=%22cpu%22%20%22identification%22%20%22identif%22%20%22mask%22%20
0
0