 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Real (and Virtual) Adventures of Nathan the IT Guy &#187; ps auxfww | grep</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/information-technology/tag/ps-auxfww-grep/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/information-technology</link>
	<description></description>
	<lastBuildDate>Fri, 17 May 2013 13:18:20 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>How to Properly kill a VM</title>
		<link>http://itknowledgeexchange.techtarget.com/information-technology/how-to-properly-kill-a-vm/</link>
		<comments>http://itknowledgeexchange.techtarget.com/information-technology/how-to-properly-kill-a-vm/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 15:42:11 +0000</pubDate>
		<dc:creator>Nathan Simon</dc:creator>
				<category><![CDATA[ESX Server 3.5]]></category>
		<category><![CDATA[how to find the PID of a vm]]></category>
		<category><![CDATA[kill -9 PID]]></category>
		<category><![CDATA[PID]]></category>
		<category><![CDATA[ps -ef |grep]]></category>
		<category><![CDATA[ps auxfww | grep]]></category>
		<category><![CDATA[vm won't respond]]></category>
		<category><![CDATA[vmware]]></category>
		<category><![CDATA[vmware-cmd]]></category>
		<category><![CDATA[vmware-cmd stop]]></category>
		<category><![CDATA[vmware-cmd stop hard]]></category>
		<category><![CDATA[vmx]]></category>
		<category><![CDATA[vsphere]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/information-technology/how-to-properly-kill-a-vm/</guid>
		<description><![CDATA[We all know that you can use the command &#8220;ps -ef &#124;grep (vmconfig filename.vmx)&#8221; to find the PID for a VM, but I get confused as to which number that comes up is actually the PID&#8230; I found a new command that works much better. See below. The Definitive way to Kill a PID process [...]]]></description>
				<content:encoded><![CDATA[<p>We all know that you can use the command &#8220;<strong>ps -ef |grep (vmconfig filename.vmx)</strong>&#8221; to find the PID for a VM, but I get confused as to which number that comes up is actually the PID&#8230; I found a new command that works much better. See below.</p>
<p>The Definitive way to Kill a PID process</p>
<p>The steps below are based on the fact that you already tried to use &#8220;vmware-cmd vmname.vmx stop; stop hard&#8221;</p>
<p>1.)    A final solution is to kill the PID (process ID). Issue the following command: &#8220;<strong>ps auxfww | grep &lt;vmname&gt;</strong>&#8221; to locate the correct PID (BTW: this cannot be done via *ESXTOP*). The <strong>first number</strong> to appear in the output is your PID. The PID can be used to terminate the process by issuing kill -9 PID.</p>
<p>2.)    Run vmware-cmd &lt;vmname&gt;.vmx getstate to see if it is now &#8220;off&#8221;, as it should be.</p>
<p>3.)    You can now go back into Virtual Infrastructure Client and start the machine.</p>
<p>-NS</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/information-technology/how-to-properly-kill-a-vm/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
