What are two requirements to enable EVC in vSphere DRS cluster? (Choose two.)
A.
CPUs must be from the same vendor.
B.
EVC must use the lowest possible baseline supported by the hardware.
C.
CPUs must be in the same family and of the same speed.
D.
No VMs may be running in the cluster.
Explanation:
https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUIDFEC87C0B-7276-4152-8EAA-915305E64FED.html#GUID-FEC87C0B-7276-4152-8EAA-915305E64FED
A is ok, why not D?
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-FEC87C0B-7276-4152-8EAA-915305E64FED.html
1
0
B is correct because EVC ensures that all hosts in a cluster present the same CPU feature set to virtual machines, even if the actual CPUs on the hosts differ and prevents vMotion from failing because of incompatible CPUs.
When you configure EVC, you configure all host processors in the cluster to present the feature set of a baseline processor. In other words, the feature set must be common in all the CPUs hence lowest possible baseline. EVC masks only those processor features that affect vMotion compatibility.
A is correct because CPU req is A single vendor, either AMD or Intel.
D is NOT correct because you can power off (and back on later) all virtual machines in the cluster that are running on hosts with a feature set greater than the EVC mode that you intend to enable. You can also migrate these virtual machines out of the cluster.
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-9F444D9B-44A0-4967-8C07-693C6B40278A.html
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-FEC87C0B-7276-4152-8EAA-915305E64FED.html
4
0
This should be A & D in my opinion
https://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_admin_guide.pdf
Page 239
3
5
Esx 3.5 was way back. We are now at ESXi 6.5
Welcome to 2018.
7
1
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-E3F5BAFE-EB14-408D-999A-590D4337D59C.html
AD
1
4
AB
A – https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-FEC87C0B-7276-4152-8EAA-915305E64FED.html
“A single vendor, either AMD or Intel.”
B – https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-9F444D9B-44A0-4967-8C07-693C6B40278A.html
“The EVC mode must be equivalent to, or a subset of, the feature set of the host with the smallest feature set in the cluster”
Not D, because in 6.5 it seems you only need to power off/vMotion the VMs “running on hosts with a feature set greater than the EVC mode that you intend to enable.”
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-FEC87C0B-7276-4152-8EAA-915305E64FED.html
6
1
But ‘equivalent to … host with the smallest feature set’ and ‘lowest possible baseline supported’ are different answers.
The first would be the highest possible feature set considering the host capabilities (e.g. Westmere). The second would be the lowest possible feature set for that vendor (e.g. Merom).
My vote is also for A and D.
0
1
To raise the EVC mode from a CPU baseline with fewer features to one with more features, you do not need to turn off any running virtual machines in the cluster. Virtual machines that are running do not have access to the new features available in the new EVC mode until they are powered off and powered back on. A full power cycling is required. Rebooting the guest operating system or suspending and resuming the virtual machine is not sufficient.
To lower the EVC mode from a CPU baseline with more features to one with fewer features, you must first power off any virtual machines in the cluster that are running at a higher EVC mode than the one you intend to enable, and power them back on after the new mode has been enabled.
4
0
B says “supported by the hardware”, not the vendor.
So, if the hosts in the cluster all have, for example, Ivy Bridge, you can enable EVC up to Ivy Bridge generation.
IF you match EVC mode with the same generation of the hosts, then there is NO need to power off the VM.
If you set an older generation, then you need to power off any VM on the hosts newer than that generation.
e.g. Host A: Ivy bridge, 1 VM running
Host B: Haswell, 0 VM running
EVC to Ivy bridge: OK (as long as no VM running on Host B)
EVC to Sandy bridge: need to power off VM first
EVC to Haswell: not supported
So in this A and B are correct.
1
1