ESX Server 3.5

How to Properly kill a VM

We all know that you can use the command “ps -ef |grep (vmconfig filename.vmx)” to find the PID for a VM, but I get confused as to which number that comes up is actually the PID… I found a new command that works much better. See below.

The Definitive way to Kill a PID process

The steps below are based on the fact that you already tried to use “vmware-cmd vmname.vmx stop; stop hard”

1.)    A final solution is to kill the PID (process ID). Issue the following command: “ps auxfww | grep <vmname>” to locate the correct PID (BTW: this cannot be done via *ESXTOP*). The first number to appear in the output is your PID. The PID can be used to terminate the process by issuing kill -9 PID.

2.)    Run vmware-cmd <vmname>.vmx getstate to see if it is now “off”, as it should be.

3.)    You can now go back into Virtual Infrastructure Client and start the machine.

-NS

Windows XP and VMware ESX Server

Okay I have seen this a lot, and I have also solved this myself, but I’m going to be honest with you when installing Windows XP Pro on an ESX Server and using the LSI Drivers, you will have issues. There is a driver on LSI’s website that you can use, but I don’t have that information for you at the moment, I do however have another solution, using the BusLogic controller, you can utilize a flp image file that is already located on the datastore. Alot of websites say, use an LSI Logic controller and the floppy image and you will be fine, well thats wrong. This is in fact a virtual floppy for the BusLogic controller.

So basically, start the setup of Windows XP Pro whichever way you want, hit F6 and when it asks for the floppy, mount the flp file from the data store, connect it, then hit “S” to proceed. The BusLogic driver should load and you will then be able to proceed with the installation.

Also on a side note… if you decide to VMconvert Windows XP Pro you will not have any luck, I haven’t had a chance to experiment too much, but I think if you select BusLogic(on the VM Properties) on before conversion you might be Ok. If anyone can answer this for me that would be great. Last time I VMConverted a Windows XP box I was greeted with a lovely BSOD!

Here is a good reference link to check out if your having issues.

NS