Windows DatabaseebooksStatistical Information

LLE10150 : VMware ESX: virtual machine does not start.

Symptom:

Error message: : "Faild to power on <VMName> on <ESXName> in <Datacenter>: Could not power on VM : No swap file."

Cause:

The swap file does still exist and is locked from an obsolete ("hanging") process on same or other ESX server

Solution:

This error occurs, when a VM is tried to be powered on, while another ESX host still has one or more files open. This can happen after an unsuccessful HA (failover) because of a crash or fault. Even if the following procedure helps, you should try to find the initial problem, since it might be some bigger issue in your HA/DRS!

How to fix this error:

Log in to each (!) ESX-service console and look for a process of your faulty VM still running (your VM-Name in italic):
ESX 2.x and 3.0: ps -ef | grep vm-name
ESX 3.5: ps -efwww | grep vm-name

If you get something like the following, it's the process prohibiting your VM to start:

root 1915 1 0 12:03 ? 00:00:00 /usr/lib/vmware/bin/vmkload_app /usr/lib/vmware/bin/vmware-vmx -ssched.group=host/user -# name=VMware ESX Server;version=3.5.0;licensename=VMware ESX Server;licenseversion=2.0 build-82663; -@ pipe=/tmp/vmhsdaemon-0/vmx69b380c12d811cae; /vmfs/volumes/28620f6e-6be3a1de-5cb1-001eb9c1b11a/vm-name/vm-name.vmx

The above (example!!!) number in bold will be the process ID you might want to kill:

kill -9 pid (where pid is the process ID, 1915 in the example above).

After this, your VM should start.


Disclaimer:

The information provided in this document is intended for your information only. Lubby makes no claims to the validity of this information. Use of this information is at own risk!
Copyright © 2004-2011 Lubby (V3.0.10 Aug 2011)
Sponsored by Keskon.
Statistical information by Google Analytics