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

Acropolis Hypervisor Configuration

The following commands help to configure Factory (Nutanix) loaded hypervisor called as Acropolis without reinstalling using Foundation process: To configure IP Address:  root@ahv# vi /etc/sysconfig/network-scripts/ifcfg-br0  ONBOOT="yes"  NM_CONTROLLED="no"  PERSISTENT_DHCLIENT = 1  NETMASK =" subnet_mask "  IPADDR =" host_ip_addr "  DEVICE="br0"  TYPE="ethernet"  GATEWAY =" gateway_ip_addr "  BOOTPROTO="none“  (set as “static”) DNS Entry:  root@ahv# vi /etc/resolv.conf To List Ethernet Interfaces:   manage_ovs show_interfaces  To verify the interfaces are assigned to br0:   manage_ovs --bridge_name br0 show_uplinks  To Add 1gb Interface into br0:   manage_ovs --bond_name bond1 --interfaces 1g update_uplinks  To Configure IP Address in CVM : ssh to CVM (ssh  nutanix@192.168.5.254 ) and use sudo vi /etc/sysconfig/network-scripts/ifcfg-eth0, finally re...
Post a Comment
Read more

Set VLAN ID to IPMI Address in Nutanix

The IPMI is remote management interface like as HP iLO, DELL DRAC. During the Nutanix cluster deployment, it is not possible to mention the VLAN ID of the IPMI's IP Address. This need to be entered thru command line via ESXi host or Windows Hyper-V. This article talks about ESXi host only. Login to ESXi thru SSH client. Run the following command to enter the VLAN ID (we assume that you already configured IP Address) ~ # /ipmitool lan set 1 vlan id 333 ~ # /ipmitool lan print1 Set in Progress         : Set Complete Auth Type Support       : NONE MD2 MD5 PASSWORD  Auth Type Enable        : Callback : MD2 MD5 PASSWORD                          : User     : MD2 MD5 PASSWORD                          : Operator : MD2 MD5 PASSWORD              ...
Post a Comment
Read more