Archive for December, 2009

Our ESX server are 3.5 Update 4 , and when I tried to power on a virtual machine I received the following error:

Solution 1:

Through the vSphere client I went to the Events tab of the virtual machine and saw the following:

I connected through SSH connection to the destination server ( which the vm was trying to be relocated to -ultravm12) and type the following: 

 vmware-cmd “/vmfs/volumes/47fc81af-e1a86f8d-6034-001b78bb373c/TLWSRecVoIP4/TLWSRecVoIP4.vmx” getstate

But I received the following error: VMControl error -11: No such virtual machine

I conclude from it that the virtual machine hasn’t been registered on the destination ESX server (ultravm12), and may never was unregistered from the source ESX (ultravm9).

I connected through SSH connection to the source ESX (ultravm9) and type the following:

vmware-cmd  “/vmfs/volumes/47fc81af-e1a86f8d-6034 001b78bb373c/TLWSRecVoIP4/TLWSRecVoIP4.vmx” getstate

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:

From the vSphere client stand on the cluster > Edit Settings > Virtual Machine Options > search the virtual machine and change the automation level into disabled.

Afterwards migrate the server to another host and power on the virtual machine.




Read Full Post »

I connected to the lab manager web interface and all of my VMs appear as unavailable

The problem was that the lab manager 4 was disconnected from the vCenter server.

I connected into the vCenter server and saw that the service was down, and started it.


Read Full Post »

I defined a role as I wanted, and connected it into a user, but when I try to login – I am stuck! I can’t pass over the login page. Don’t understand why?

The problem is due to lack of the following permissions:

Go to System > Roles and Rights > Role properties

  1. Uncheck “show only selected rights”
  2. Check overview > overview: view as shown below:


Read Full Post »


One of our ESX servers had a stuck virtual machine. I tried to restart the vpxa service (service vmwarevpxa restart) and the management service (service mgmtvmware 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:


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.


Read Full Post »


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:


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.


Read Full Post »


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:

1)      HP DL 380 G5

Please enter the BIOS and change the following:

In order to enter the BIOS please press F9 at startup.

  1. Advanced Options > Processor Options > No-Execute Memory Protection (Enabled)
  2. Advanced Options > Processor Options > Intel Virtualization Technology (Enabled)


2)      IBM x3550

Please enter the BIOS and change the following:

In order to enter the BIOS please press F1 at startup.

  1. Advanced Setup > CPU Options > Execute Disable Bit (Enabled)
  2. Advanced Setup > CPU Options > Intel Virtualization Technology (Enabled)



Read Full Post »


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:

Aug  2 14:51:42 ultravm12 watchdog-hostd: PID file /var/run/vmware/watchdog-hostd.PID not found


  1. Run vmware-watchdog -r hostd, If you get /var/run/vmware/watchdog-hostd.PID not found , Delete /var/run/vmware/vmware-hostd.PID
  2. Run ps -auwwwwx | grep “vmware-hostd” , Delete the process that exists. For example:  [root@ultravm12 root]# ps -auwwwwx | grep “vmware-hostd”                                                                                               root      1934  0.9 16.4 136900 44308 ?      S    Jul19 194:01 /usr/lib/vmware/hostd/vmware hostd /etc/vmware/hostd/config.xml -u                                                                                                                                     root     31287  0.0  0.2  3708  676 pts/0    S    15:04   0:00 grep vmware-hostd                                            [root@ultravm12 root]# kill -9 1934
  3. Check if the timestamp of the file watchdog-hostd.PID  has changed
  4. ls -lah /var/run/vmware/watchdog-hostd.PID
  5. Run service mgmt-vmware restart
  6. Make sure that /var/run/vmware/vmware-hostd.PID was recreated


Read Full Post »

Older Posts »