Monday, May 3, 2010

Killing a non responsive VM

Troubleshooting (Various things ran into within our environment and how to resolve them or investigate)Open a case with Vmware -1-877-4VMWAREU

VConverter -
Conversion Stops with Disk corrupted error around 4-6%This is usually due to something using the disk not allowing VConvert to access the file or bit. This is commonly due to an application lock (ie: Symantec or SQL) - Stop all non Microsoft services and run the converter again - Use the CloneCD option (boot from CD to convert) Conversion Stops at 97%The Conversion is complete. The converter has an issue writing the final configurations to the VM. Run the VConverter again and choose the Configure Machine option. This will take some time. It will basically reconfig the VM with no drivers. After VM boot it will then start to install the rest of the drivers for NICs, Procs, etc...

Killing a non responsive VM (VM boot wont turn off or on via VCenter)
open WINSCPConnect to AZ84ESXDEV01account vmadminenter passwordopen a Putty shellenter password (uses the same account "vmadmin")Type su -enter root account passwordType ps -ef grep The second column is your pid Type kill -9 Type ps -ef grep again to verify no processesCheck VM state again, it should now be offTo Power On the VM you can use the VI client orType vmware-cmd //server.vmx start to power on VM

1 comment:

  1. Killing a non responsive VM (VM boot wont turn off or on via VCenter)
    open WINSCP
    Connect to AZ84ESXDEV01
    account vmadmin
    enter password
    open a Putty shell
    enter password (uses the same account "vmadmin")
    Type su -
    enter root account password
    Type ps -ef | grep
    The second column is your pid
    Type kill -9
    Type ps -ef | grep again to verify no processes

    Check VM state again, it should now be off

    To Power On the VM you can use the VI client or

    ReplyDelete