Regardless of whether you use a cluster or not, don’t forget to back up your VMs. Enabling the EVC Mode for the vCenter VM.
How to Enable the EVC Mode in the Cluster Without Downtime.Checking Configuration of the EVC Mode in PowerCLI.VMware vSphere Version / CPU compatibility for EVC.Today’s blog post covers the EVC mode functionality and contains the following sections: This is possible due to the Enhanced vMotion Capability (EVC) feature that can be enabled for clusters in VMware vSphere. There is no reason to worry – you can use High Availability clusters in vSphere, add nodes with different processors, and use vMotion for virtual machine live migration between hosts that have different processors. The processors you bought 3 years ago are not being produced at present and are no longer sold in the market you can buy only the processors of the newest family. This is a common situation – imagine that you have a cluster with 5 ESXi nodes you bought 3 years ago and you need to add two more nodes to run more VMs for meeting your business needs.
VMware designed their vSphere software with regard to the situations that can occur in the production environment, including expanding a cluster by adding new servers with different processors. Otherwise, you are likely to get an error when using vMotion. Moreover, the strict requirement is that the processors must be manufactured by the same vendor, such as Intel or AMD. If you want to use servers with different processor models in the cluster, it is better to deploy processors of the same generation. If you are familiar with the vMotion feature, you probably remember that the recommended practice is to use the same processors on all ESXi servers for VM live migration. I’m sure that this was some of the ugliest fault-finding any VMWare Administrator has ever seen and any VCP’s reading this will be curled up in the corner, screaming “find a happy place”.By Michael Bose How VMware EVC Mode Works: Complete Overview Once I had don that, I repeated the first step of the day by manually removing the VM from Inventory and re-adding it again via browsing to the DataStore.
To remove the VM from the old host, run command: vmware-cmd –s unregister /vmfs/volumes//VMDIR>/.vmx.
I chose the easiest option first – Check to see if the offending ESX host (identified by MAC Address) was still trying to manage that VM. I suspected that a transfer between Hosts had not been successful. There are a number of situations that can cause another ESX Host to lock the files of a VM. In my case, it was another of my ESX hosts the bolded number in there is the MAC address of the offending machine that has a lock on those files.here is an example of the log file from a VMWare article.Alas, as my Hosts are still ESX 4.0, I would then have to look at the System Logs instead of on-screen.ran command: vmkfstools -D /vmfs/volumes///.xxx.Back to the command-line! To look for the culprit, I did the following: So now I know that the VM was invalid because of some locked files and now it was time to find out who had locked the files and how to unlock them. any files that provided a result of device or resource busy was a locked file.To check what files were locked, i ran the command: touch *.
Ordinarily, I would have had a go at fixing it straight away but is is an archive server that is not actually in use so it has been down the priority list. We’ve had a Virtual Machine showing up in vCenter Server as Invalid (and greyed out) for a few days now.