<?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; ESX4</title>
	<atom:link href="http://wjpatton.com/index.php/tag/esx4/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>VMware vSphere Hardening Guide &#8211; Draft Rev. B</title>
		<link>http://wjpatton.com/index.php/2010/01/vmware-vsphere-hardening-guide-draft-rev-b/</link>
		<comments>http://wjpatton.com/index.php/2010/01/vmware-vsphere-hardening-guide-draft-rev-b/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 15:46:54 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[hardening]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=223</guid>
		<description><![CDATA[VMware has released a draft of the vSphere Hardening Guide, and are encouraging feedback from the community.  It is broken into multiple pieces.
Part 1: Introduction
Part 2: Virtual Machines
Part 3: Host
Part 4: vNetwork
Part 5: vCenter
Part 6: COS
]]></description>
			<content:encoded><![CDATA[<p>VMware has released a draft of the vSphere Hardening Guide, and are encouraging feedback from the community.  It is broken into multiple pieces.</p>
<p>Part 1: <a href="http://communities.vmware.com/docs/DOC-11843;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">Introduction</a></p>
<p>Part 2: <a href="http://communities.vmware.com/docs/DOC-11844;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">Virtual Machines</a></p>
<p>Part 3: <a href="http://communities.vmware.com/docs/DOC-11845;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">Host</a></p>
<p>Part 4: <a href="http://communities.vmware.com/docs/DOC-11846;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">vNetwork</a></p>
<p>Part 5: <a href="http://communities.vmware.com/docs/DOC-11847;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">vCenter</a></p>
<p>Part 6: <a href="http://communities.vmware.com/docs/DOC-11848;jsessionid=9A1CD2E78A2DBFBE2333677F76B5EE56" target="_blank">COS</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/01/vmware-vsphere-hardening-guide-draft-rev-b/feed/</wfw:commentRss>
		<slash:comments>0</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 ESX4 Update 01 Removed from Update Manager</title>
		<link>http://wjpatton.com/index.php/2009/11/vmware-esx4-update-01-removed-from-update-manager/</link>
		<comments>http://wjpatton.com/index.php/2009/11/vmware-esx4-update-01-removed-from-update-manager/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 18:35:34 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX4]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=206</guid>
		<description><![CDATA[If you are looking to update your ESX4 hosts to Update 01, don&#8217;t look in Update Manager.  VMware has removed the update because of a bug with the HP Management Agents preventing the update from completely successfully and rendering the host inoperable.
From KB1016070:
&#8220;Note: If you want to install the update, you must download the update manually. [...]]]></description>
			<content:encoded><![CDATA[<p>If you are looking to update your ESX4 hosts to Update 01, don&#8217;t look in Update Manager.  VMware has removed the update because of a bug with the HP Management Agents preventing the update from completely successfully and rendering the host inoperable.</p>
<p>From <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1016070" target="_blank">KB1016070</a>:</p>
<p>&#8220;<strong>Note</strong>: If you want to install the update, you must download the update manually. The update is no longer available for automatic download in Update Manager and the vSphere Update Utility. You can find the update on the <a href="http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vsphere_4/4" target="_blank">VMware Downloads</a> site and copy the download to your local depot as needed.&#8221;</p>
<p>Note:  ESXi 4 is unaffected by this KB.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/11/vmware-esx4-update-01-removed-from-update-manager/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1016070 &#8211; ESX 4 Update 01 and HP Management Agents Failed Upgrade</title>
		<link>http://wjpatton.com/index.php/2009/11/vmware-kb1016070-esx-4-update-01-and-hp-management-agents-failed-upgrade/</link>
		<comments>http://wjpatton.com/index.php/2009/11/vmware-kb1016070-esx-4-update-01-and-hp-management-agents-failed-upgrade/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 18:26:12 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[KB]]></category>
		<category><![CDATA[SIM]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=204</guid>
		<description><![CDATA[VMware has posted a bug when upgrading ESX 4 to Update 01 with HP Management Agents running.  (ESXi is unaffected)
You may have your host end the update unsuccessfully, and in a non-responsive state.  To avoid this, disable all the HP Management Agents prior to running the update.
Read the full article here.
]]></description>
			<content:encoded><![CDATA[<p>VMware has posted a bug when upgrading ESX 4 to Update 01 with HP Management Agents running.  (ESXi is unaffected)</p>
<p>You may have your host end the update unsuccessfully, and in a non-responsive state.  To avoid this, disable all the HP Management Agents prior to running the update.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1016070" target="_blank">Read the full article here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/11/vmware-kb1016070-esx-4-update-01-and-hp-management-agents-failed-upgrade/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1009607 &#8211; Pegasus CIMSERVER Memory Leak</title>
		<link>http://wjpatton.com/index.php/2009/11/vmware-kb1009607-pegasus-cimserver-memory-leak/</link>
		<comments>http://wjpatton.com/index.php/2009/11/vmware-kb1009607-pegasus-cimserver-memory-leak/#comments</comments>
		<pubDate>Fri, 06 Nov 2009 20:56:26 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[CIM]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[KB]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=199</guid>
		<description><![CDATA[VMware has acknowledged an issue that we have been battling for some time with a Pegasus CIMSERVER memory leak.  It has been fixed under ESX 4, as it does not use Pegasus, otherwise setup a CRON job for restart Pegasus periodically.
This issue has been extremely frustrating in our environment for a very long time, and [...]]]></description>
			<content:encoded><![CDATA[<p>VMware has acknowledged an issue that we have been battling for some time with a Pegasus CIMSERVER memory leak.  It has been fixed under ESX 4, as it does not use Pegasus, otherwise setup a CRON job for restart Pegasus periodically.</p>
<p>This issue has been extremely frustrating in our environment for a very long time, and initially we suspected that HP SIM may be to blame, turns out we may have gotten that wrong.</p>
<p>We have worked with VMware Support many times, and this is the first time they have acknowledged this leak and that HP SIM is not the culprit.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1009607" target="_blank">Read the KB here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/11/vmware-kb1009607-pegasus-cimserver-memory-leak/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>VCP vSphere Practise Exam</title>
		<link>http://wjpatton.com/index.php/2009/09/vcp-vsphere-practise-exam/</link>
		<comments>http://wjpatton.com/index.php/2009/09/vcp-vsphere-practise-exam/#comments</comments>
		<pubDate>Thu, 10 Sep 2009 14:54:51 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[vcp]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=165</guid>
		<description><![CDATA[Simon Long of The Slog has posted a VCP vSphere Practise Exam built out of VMware documentation and personal information and experience.  Looks great, I plan on taking it tonight to brush up!
Take the Exam here.
VCP vSphere Practise Exam]]></description>
			<content:encoded><![CDATA[<p>Simon Long of <a href="http://www.simonlong.co.uk/blog" target="_blank">The Slog</a> has posted a VCP vSphere Practise Exam built out of VMware documentation and personal information and experience.  Looks great, I plan on taking it tonight to brush up!</p>
<p><a href="http://www.simonlong.co.uk/blog/vcp-vsphere-4-practice-exam/" target="_blank">Take the Exam here.</a></p>
<a href='http://wjpatton.com/index.php/2009/09/vcp-vsphere-practise-exam/' class='retweet ' startCount = '0'>VCP vSphere Practise Exam</a>]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/09/vcp-vsphere-practise-exam/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware Tech Resource: vSphere Memory Management</title>
		<link>http://wjpatton.com/index.php/2009/09/vmware-tech-resource-vsphere-memory-management/</link>
		<comments>http://wjpatton.com/index.php/2009/09/vmware-tech-resource-vsphere-memory-management/#comments</comments>
		<pubDate>Thu, 10 Sep 2009 00:05:00 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[Virtualization]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=141</guid>
		<description><![CDATA[VMware has released a new white page on memory management techniques within ESX/i 4.  The previous version for 3.x was a great resource for many discussions, troubleshooting, and designs over the past few years.  This new document is every bit as good, but has even better documentation and examples with greater technical information.
Read the whitepaper [...]]]></description>
			<content:encoded><![CDATA[<p>VMware has released a new white page on memory management techniques within ESX/i 4.  The previous version for 3.x was a great resource for many discussions, troubleshooting, and designs over the past few years.  This new document is every bit as good, but has even better documentation and examples with greater technical information.</p>
<p><a href="http://www.vmware.com/resources/techresources/10062" target="_blank">Read the whitepaper here.</a></p>
<a href='http://wjpatton.com/index.php/2009/09/vmware-tech-resource-vsphere-memory-management/' class='retweet ' startCount = '0'>VMware Tech Resource: vSphere Memory Management</a>]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/09/vmware-tech-resource-vsphere-memory-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1003490 &#8211; Restarting ESX Management Agents</title>
		<link>http://wjpatton.com/index.php/2009/09/vmware-kb1003490-restarting-esx-management-agents-2/</link>
		<comments>http://wjpatton.com/index.php/2009/09/vmware-kb1003490-restarting-esx-management-agents-2/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 17:53:17 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[agents]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[KB]]></category>
		<category><![CDATA[management]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=136</guid>
		<description><![CDATA[You will find these instructions in other How To posts and links here, but I thought I would post a simple KB from VMware for quick reference.  service mgmt-vmware restart, will NOT cause a Guest to reboot or go down.
Click here for the article.
]]></description>
			<content:encoded><![CDATA[<p>You will find these instructions in other How To posts and links here, but I thought I would post a simple KB from VMware for quick reference.  service mgmt-vmware restart, will NOT cause a Guest to reboot or go down.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1003490" target="_blank">Click here for the article.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/09/vmware-kb1003490-restarting-esx-management-agents-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware Tech Resource:  vSphere 4 CPU Scheduler in ESX 4</title>
		<link>http://wjpatton.com/index.php/2009/09/vmware-tech-resource-vsphere-4-cpu-scheduler-in-esx-4/</link>
		<comments>http://wjpatton.com/index.php/2009/09/vmware-tech-resource-vsphere-4-cpu-scheduler-in-esx-4/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 23:13:37 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=119</guid>
		<description><![CDATA[VMware document defining Scheduler process improvements, and changes for ESX 4.  There are some very significant changes, and there are always many customer, client, and user questions about how ESX handles the Scheduler functions.
Get the document here.
]]></description>
			<content:encoded><![CDATA[<p>VMware document defining Scheduler process improvements, and changes for ESX 4.  There are some very significant changes, and there are always many customer, client, and user questions about how ESX handles the Scheduler functions.</p>
<p><a href="http://www.vmware.com/resources/techresources/10059" target="_blank">Get the document here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/09/vmware-tech-resource-vsphere-4-cpu-scheduler-in-esx-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
