<?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>WJPatton.com &#187; esx</title>
	<atom:link href="http://wjpatton.com/index.php/tag/esx/feed/" rel="self" type="application/rss+xml" />
	<link>http://wjpatton.com</link>
	<description></description>
	<lastBuildDate>Mon, 19 Jul 2010 14:45:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>VMware KB1007566 &#8211; Monitor Snapshot Deletion</title>
		<link>http://wjpatton.com/index.php/2010/04/vmware-kb1007566-monitor-snapshot-deletion/</link>
		<comments>http://wjpatton.com/index.php/2010/04/vmware-kb1007566-monitor-snapshot-deletion/#comments</comments>
		<pubDate>Wed, 28 Apr 2010 19:03:11 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[snapshot]]></category>
		<category><![CDATA[timeout]]></category>
		<category><![CDATA[vmdk]]></category>
		<category><![CDATA[vmfs]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=242</guid>
		<description><![CDATA[VMware updated a KB today on how to monitor snapshot deletion.  This is especially useful for large snapshots that &#8220;time out&#8221; for vCenter because they take more than 5-10 minutes to complete.  I have been using this exact procedure for years and never thought to blog it&#8230;for some insane reason.
Read the KB here.
Basically, use the [...]]]></description>
			<content:encoded><![CDATA[<p>VMware updated a KB today on how to monitor snapshot deletion.  This is especially useful for large snapshots that &#8220;time out&#8221; for vCenter because they take more than 5-10 minutes to complete.  I have been using this exact procedure for years and never thought to blog it&#8230;for some insane reason.</p>
<p>Read the KB <a href="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;docType=kc&amp;externalId=1007566" target="_blank">here</a>.</p>
<p>Basically, use the watch command on the *.vmdk files in the VM datastore.  You can use -n to set a refresh interval and -d to show the change in size between refreshes.  However, the most important information is what base .vmdk file is being written to and when.  This touch timestamp will give you more information on which disk is in progress, which has not yet started, and what is already done.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/04/vmware-kb1007566-monitor-snapshot-deletion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interpreting ESXTOP files with ESXPlot</title>
		<link>http://wjpatton.com/index.php/2010/02/interpreting-esxtop-files-with-esxplot/</link>
		<comments>http://wjpatton.com/index.php/2010/02/interpreting-esxtop-files-with-esxplot/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 04:14:32 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[drummonds]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[esxplot]]></category>
		<category><![CDATA[esxtop]]></category>
		<category><![CDATA[perfmon]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[vpivot]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=234</guid>
		<description><![CDATA[Scott Drummonds of vPivot.com posted on ESXPlot, a great tool that is far more efficient and less aggravating than Perfmon for working with ESXTOP output files.
Geoff White has created a badly needed tool here, Perfmon worked but was very time consuming.  Especially with those days or weeks of ESXTOP statistic files.
Extract and use the README.  For Windows, extract all [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://twitter.com/drummonds" target="_blank">Scott Drummonds</a> of <a href="http://vpivot.com" target="_blank">vPivot.com</a> posted on <a href="http://vpivot.com/2010/01/13/esxplot-1-0-released/" target="_blank">ESXPlot</a>, a great tool that is far more efficient and less aggravating than Perfmon for working with ESXTOP output files.</p>
<p>Geoff White has created a badly needed tool here, Perfmon worked but was very time consuming.  Especially with those days or weeks of ESXTOP statistic files.</p>
<p>Extract and use the README.  For Windows, extract all files, navigate to the esxplot.exe in the Bin directory and you are off and running!</p>
<p>Geoff White now has a full project site with all information and releases.  <a href="http://www.durganetworks.com/esxplot" target="_blank">Click here</a></p>
<p>Labs.vmware.com has now gone live and hosting ESXPlot as well.  <a href="http://labs.vmware.com/flings/esxplot" target="_blank">Click here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/02/interpreting-esxtop-files-with-esxplot/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>VMware KB1011170 &#8211; Checking Zero vs EagerZero Disk Status</title>
		<link>http://wjpatton.com/index.php/2010/01/vmware-kb1011170-checking-zero-vs-eagerzero-disk-status/</link>
		<comments>http://wjpatton.com/index.php/2010/01/vmware-kb1011170-checking-zero-vs-eagerzero-disk-status/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 18:43:59 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[esxi4]]></category>
		<category><![CDATA[KB]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=220</guid>
		<description><![CDATA[VMware has released a KB with a handy vmfstools command to check your VM&#8217;s disk status.  If the VMFS output shows a &#8220;Z&#8221; it is Zerothick with blocks that have not been written to yet.
Read the article here.
This allows you to check the disk status for options such as Fault Tolerance or Microsoft Cluster Services.  [...]]]></description>
			<content:encoded><![CDATA[<p>VMware has released a KB with a handy vmfstools command to check your VM&#8217;s disk status.  If the VMFS output shows a &#8220;Z&#8221; it is Zerothick with blocks that have not been written to yet.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1011170" target="_blank">Read the article here.</a></p>
<p>This allows you to check the disk status for options such as Fault Tolerance or Microsoft Cluster Services.  The disks must be in an Eagerzerothick format for these options to work.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/01/vmware-kb1011170-checking-zero-vs-eagerzero-disk-status/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB 1008886 &#8211; Unable to read partition from Add Storage Wizard</title>
		<link>http://wjpatton.com/index.php/2009/10/vmware-kb-1008886-unable-to-read-partition-from-add-storage-wizard/</link>
		<comments>http://wjpatton.com/index.php/2009/10/vmware-kb-1008886-unable-to-read-partition-from-add-storage-wizard/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 20:46:23 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[KB]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=197</guid>
		<description><![CDATA[These are great instructions if you have received errors when trying to add a LUN to an ESX Host, and suspect that the LUN may not be READY, or write enabled these instructions can help you troubleshoot and/or fix the LUN.
Read the KB here.
If you are unable to re-write the LUN label, the disk is [...]]]></description>
			<content:encoded><![CDATA[<p>These are great instructions if you have received errors when trying to add a LUN to an ESX Host, and suspect that the LUN may not be READY, or write enabled these instructions can help you troubleshoot and/or fix the LUN.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1008886" target="_blank">Read the KB here.</a></p>
<p>If you are unable to re-write the LUN label, the disk is not READY or not write enabled.  Otherwise, if the label is something other than msdos, it should now be able to be added after following these instructions.</p>
<p>*Warning* Using Parted incorrectly could destroy data on LUNs in use, if not used properly!</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/10/vmware-kb-1008886-unable-to-read-partition-from-add-storage-wizard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1005184 &#8211; Decoding ESX Purple Screen Error</title>
		<link>http://wjpatton.com/index.php/2009/09/vmware-kb1005184-decoding-esx-purple-screen-error/</link>
		<comments>http://wjpatton.com/index.php/2009/09/vmware-kb1005184-decoding-esx-purple-screen-error/#comments</comments>
		<pubDate>Tue, 22 Sep 2009 23:38:23 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[KB]]></category>
		<category><![CDATA[PSOD]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=191</guid>
		<description><![CDATA[VMware doesn&#8217;t use the &#8220;Purple Screen of Death&#8221; or &#8220;ESX PSOD&#8221; terminology in their documents so if you Google it, you won&#8217;t get directed to VMware.com and this document for this information.  I know in the past I have spent far too much time searching for PSOD information, so keep this link handy. This document [...]]]></description>
			<content:encoded><![CDATA[<p>VMware doesn&#8217;t use the &#8220;Purple Screen of Death&#8221; or &#8220;ESX PSOD&#8221; terminology in their documents so if you Google it, you won&#8217;t get directed to VMware.com and this document for this information.  I know in the past I have spent far too much time searching for PSOD information, so keep this link handy. This document applies to all versions of ESX, from 1.x to 4.x.</p>
<p>Thank you to <a href="http://twitter.com/vmwarecares" target="_blank">Rick Blythe</a> of <a href="http://www.vmware.com" target="_blank">VMware</a> for the link from the <a href="http://communities.vmware.com/thread/233036" target="_blank">VMTN Community</a> site.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1005184" target="_blank">Document located here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/09/vmware-kb1005184-decoding-esx-purple-screen-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
