<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Fixing VMware &#8220;no swap file&#8221; VM power-on failures</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/virtualization-pro/fixing-vmware-no-swap-file-vm-power-on-failures/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/fixing-vmware-no-swap-file-vm-power-on-failures/</link>
	<description>A SearchVMware.com blog</description>
	<pubDate>Fri, 27 Nov 2009 17:54:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Edward L. Haletky</title>
		<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/fixing-vmware-no-swap-file-vm-power-on-failures/#comment-159</link>
		<dc:creator>Edward L. Haletky</dc:creator>
		<pubDate>Sun, 15 Mar 2009 16:22:57 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/virtualization-pro/?p=642#comment-159</guid>
		<description>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 &#124; grep VMName&#124;awk '{print $1}'&#124;awk -F= '{print $2}`
vm-support -Z $VMID

or if you want to kill with out generating files:

 VMID=`/usr/bin/vm-support -x &#124; grep VMName&#124;awk '{print $1}'&#124;awk -F= '{print $2}`
KVMID=`cat /proc/vmware/vm/$VMID/cpu/status &#124;awk '{print $1}'&#124;grep -v group&#124;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?</description>
		<content:encoded><![CDATA[<p>There is also several other ways, since the ability to use &#8216;ps auxfww&#8217;  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.</p>
<p>VMID=`/usr/bin/vm-support -x | grep VMName|awk &#8216;{print $1}&#8217;|awk -F= &#8216;{print $2}`<br />
vm-support -Z $VMID</p>
<p>or if you want to kill with out generating files:</p>
<p> VMID=`/usr/bin/vm-support -x | grep VMName|awk &#8216;{print $1}&#8217;|awk -F= &#8216;{print $2}`<br />
KVMID=`cat /proc/vmware/vm/$VMID/cpu/status |awk &#8216;{print $1}&#8217;|grep -v group|awk -F. &#8216;{print $2}&#8217;`<br />
/usr/lib/vmware/bin/vmkload_app -k 9 $KVMID </p>
<p>I am sure there are also some other ways, perhaps using the RCLI?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->