Hello. I have strange issue with vcenter 6.5. I created clusted with EVC mode to Ivy Bridge and trying to add Supermicro X10DRL-i with 2620v4 CPUs (obviously newer than ivy bridge). And i get an error saying that CPUs on target host are missings feathers, i double check bios and everythign is enabled there.
Also trying to add E3-1240 V2 host to this cluster and get same error.. Please where to look?
Ok.
Try in another way - create a cluster without EVC, add host to it and then enable EVC.
Hi!
What is VC build you use? And what is ESXi build number?
Do you have running VMs on host you trying to add into cluster? Is that host is already managed by vcenter?
Hi! 2620v4 host is running only vcenter machine, 1241v2 host doesnt run any vms.
Vcenter is: 6.5.0-7515524
both hosts are: 6.5.0.update01-5969303
Not sure whether this helps, but IMO the latest reply at Re: VCSA 6.5 7515524 any one having issues with adding hosts to existing EVC cluster. (disabling/enabling EVC) sounds helpful.
Maybe worth a try, but it's up to you.
André
Could it be that Intel Microcode updates have been applied to some hosts (via BIOS update or January ESXi patches) ? These add new CPU features.
Sadly that didnt help, tried both last and pre-last advices..
Try to update ESXi hosts to the latest available build - 7388607.
i upgraded hosts, rebooted VCSA - no success... I dont get it really.
Ok.
Try in another way - create a cluster without EVC, add host to it and then enable EVC.
Jeeesus... this worked. Really... why 6.5 is soooooo tough. Doesnt feel like enterprise to me now. Never had any problems with 5.5.
The soultion was: upgrade all hosts to latest release (i believe that was required), then turn off EVC -> add hosts -> turn on EVC
Some other users report issues with EVC when they couldn't add new hosts to existing EVC cluster
VCSA 6.5 7515524 any one having issues with adding hosts to existing EVC cluster.
Here is root cause and simple workaround for empty/existing EVC cluster issue: http://vthinkbeyondvm.com/adding-host-empty-evc-cluster-fails-simple-workaround/
It's better to create a KB article for this issue.
This is expected behaviour when running VCSA 6.5 Upd 1e (although, VMware made it easy to miss this information..)
VMware vCenter Server 6.5 Update 1e Release Notes -> under resolved issues -> security issues, see link to VMSA-2018-0004.2
* The new versions of vCenter Server set restrictions on ESXi hosts joining an Enhanced vMotion Cluster, see VMware Knowledge Base article 52085 for details.
The patches which exposed the necessary patches (ESXi650-201801401-BG & ESXi650-201801402-BG) have been withdrawn, so workaround would be as already suggested in this thread; disable EVC - Add host to cluster - re-enable EVC
A big mess, all of this Spectre/Meltdown patches... :smileyplain: