Skip to main content

Killing a VM

Sometimes the Virtual Center won’t do the job. You virtual machine has hung and you need to kill it. Here are 2 examples of how you can kill the vm from within the service console:

The ‘VMWARE-CMD’ command
Log on to the service console and issue the following command
vmware-cmd /vmfs/volumes///.vmx stop’ you must not use the friendly datastore name. If you need to know the location of all vm’s type ‘VMWARE-CMD -l’ that will list on vm’s and the location for the corresponding vmx file.
If that fails, then try it with the hard option,
‘vmware-cmd /vmfs/volumes///.vmx stop hard’ this command will just try and kill it without shutting it down.

2. Kill it using the PID command
Run the following command: ps auxfww | grep to locate the correct PID of the virtual machine, the first number to appear in the output is your vm’s PID. Use the PID number to terminate the process by issuing
kill -9 PID NO
Labels:

Comments

Post a Comment

Popular posts from this blog

vCenter Reinstallation after 60-Days trial expires without losing Database Contents

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires. We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software. This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment. When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console. Start à All Programs à Microsoft SQL Server 2005 à Configuration Tools à SQL Server Configuration Manager Creating DSN Create a System DSN f...
18 comments
Read more

Changing Thin to Thick disk and vice-versa

You can change the existing Virtual Hard disks (VMware based) from Thick to thin and vice-versa. This can be achieved by either using VMotion/SVMotion or command line tool called " vmkfstools". Using VMotion/SVMotion is required a valid license. Select “Migrate” and choose “Change Datastore” and select the Disk format. If you don’t have a VMotion/SVMotion license, use the following command to achieve the same. From Thick to Thin: vmkfstools –i "Thickdisk.vmdk" -d thin "Thindisk.vmdk" It will start to clone to virtual hard disk in Thin Provision method. After completed, you can attach this disk with VM and power it on. If all looks good, you can delete the original thick disk from the data store. Use the following command to see real-time usage of thin disk: du –h "Thindisk.vmdk" You can notice the big difference of disk usage between of Thin and Thick format disks. From Thin to Thick: vmkfstools –i "Thindisk.vmdk" -d zeroedthick "T...
3 comments
Read more

Nutanix Metro Availability - Setup Guide

Nutanix Metro Availability (MA): This new feature introduced on NOS 4.1 (Nutanix Operating System) which is really useful for the customers who is looking inexpensive DR solution especially VDI use case.  This feature allows replicate data synchronously between two sites. Lets see requirements for implementing this feature: NOS Version: NOS 4.1 or later Networking: 1.      <=5ms RTT latency 2.      3.      Bandwidth depends on “data change rate” 4.      Redundant  physical network connection Hardware: 1.      2 Nutanix clusters at each site 2.      mix/match models (eg: NX3000 at primary site and NX6000 at DR Site) Hypervisor: 1.      ESXi 5.x supported 2.      KVM/Hyper-V not now, maybe later Nutanix License: 1.   ...
2 comments
Read more