And I received an answer that the virtual machine is powered off. Then I was 100% sure that the virtual machine is still registered on the source ESX server (ultravm9).

I tried to power on the virtual machine by typing: vmware-cmd “/vmfs/volumes/47fc81af-e1a86f8d-6034 001b78bb373c/TLWSRecVoIP4/TLWSRecVoIP4.vmx” start, but I received an error. In order to solve it I unregistered the VM manually (from the source ESX – ultravm9) by typing : vmware-cmd -s unregistered “/vmfs/volumes/47fc81af-e1a86f8d-6034 001b78bb373c/TLWSRecVoIP4/TLWSRecVoIP4.vmx”

And then I registered the VM again on the same host by typing : vmware-cmd -s registered “/vmfs/volumes/47fc81af-e1a86f8d-6034 001b78bb373c/TLWSRecVoIP4/TLWSRecVoIP4.vmx”, Afterwards the VM was started successfully.

Solution 2:

Another way to solve this issue is by isolating the problematic server, and temporarily disable the virtual machine which refuse to power on from the DRS by doing the following:

One of our ESX servers had a stuck virtual machine. I tried to restart the vpxa service (service vmware–vpxa restart) and the management service (service mgmt–vmware restart) , afterwards the ESX server did not connect to the vCenter Server. No metter what I tried to do, the server refused to connect.

After restarting the vCenter server service the servie refused to strart. I restarted the vCenter Server and the service got started, I tried to connect the server again and received the following error message:

Solution

I’ve checked the licensing service and saw it was stopped and in Manual mode. I’ve change the service into Automatically and started the service.

Afterwards I connected into the ESX server through the vSphere client and refreshed its licensing. I tried again to connect the server and it worked.

One of our virtual machines appeard to be in the vCenter server with a question sign, as you can see in the photo below:

When I stood on the virtual machine in the vCenter server I saw the following error:

In the summery tab I’ve noticed that the virtual machine’s LUN has only 9GB of free space, as appears in the photo below:

Solution

I went to the inventory of LUN 74 , and moved another machine into another LUN which has enough free space. Afterwards I returned to the virtual machine’s question and pressed retry and the probelm has been solved.

Enhanced VMotion Compatibility (EVC) simplifies VMotion compatibility issues across CPU generations. EVC automatically configures server CPUs with Intel FlexMigration or AMD-V Extended Migration technologies to be compatible with older servers. After EVC is enabled for a cluster in the VirtualCenter inventory, all hosts in that cluster are configured to present identical CPU features and ensure CPU compatibility for VMotion. The features presented by each host are determined by selecting a predefined EVC baseline. VirtualCenter does not permit the addition of hosts that cannot be automatically configured to be compatible with the EVC baseline.

Hardware Changes

In order to enable VMware EVC we must first change two parameters in the server’s BIOS:

Our ESX server was disconnected from the vCenter server, I went to the following path in the ESX server in order to search through the logs what is the reason for it : /var/log/ messages , and I found the following error message: