By: Edward L. Haletky

Edward L. Haletky — Sun, 15 Mar 2009 16:22:57 +0000

There is also several other ways, since the ability to use ‘ps auxfww’ may eventually go away. That is to use something like the following which will actually suspend the VM instead of killing it, which may be better than a straight kill.

VMID=`/usr/bin/vm-support -x | grep VMName|awk ‘{print $1}’|awk -F= ‘{print $2}`
vm-support -Z $VMID

or if you want to kill with out generating files:

VMID=`/usr/bin/vm-support -x | grep VMName|awk ‘{print $1}’|awk -F= ‘{print $2}`
KVMID=`cat /proc/vmware/vm/$VMID/cpu/status |awk ‘{print $1}’|grep -v group|awk -F. ‘{print $2}’`
/usr/lib/vmware/bin/vmkload_app -k 9 $KVMID

I am sure there are also some other ways, perhaps using the RCLI?

Comments on: Fixing VMware “no swap file” VM power-on failures

By: Edward L. Haletky