<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Check and Upgrade VMware Tools</title>
	<atom:link href="http://lonesysadmin.net/2008/12/08/check-and-upgrade-vmware-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://lonesysadmin.net/2008/12/08/check-and-upgrade-vmware-tools/</link>
	<description>Virtualization, System Administration, and Technology.</description>
	<lastBuildDate>Wed, 01 Sep 2010 16:17:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Ah, Details : Bob Plankers, The Lone Sysadmin</title>
		<link>http://lonesysadmin.net/2008/12/08/check-and-upgrade-vmware-tools/comment-page-1/#comment-75462</link>
		<dc:creator>Ah, Details : Bob Plankers, The Lone Sysadmin</dc:creator>
		<pubDate>Fri, 12 Dec 2008 20:49:38 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/?p=1692#comment-75462</guid>
		<description>[...] few days ago I&#8217;d written about the fix for VMs rebooting after being VMotioned. In the comments there was some speculation about what the big problem would be for ESX 3.5 Update [...]</description>
		<content:encoded><![CDATA[<p>[...] few days ago I&#8217;d written about the fix for VMs rebooting after being VMotioned. In the comments there was some speculation about what the big problem would be for ESX 3.5 Update [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Plankers</title>
		<link>http://lonesysadmin.net/2008/12/08/check-and-upgrade-vmware-tools/comment-page-1/#comment-75442</link>
		<dc:creator>Bob Plankers</dc:creator>
		<pubDate>Wed, 10 Dec 2008 21:37:36 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/?p=1692#comment-75442</guid>
		<description>I&#039;ve got these patches applied right now, nothing too odd seems to be happening. Of course YMMV. :-)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve got these patches applied right now, nothing too odd seems to be happening. Of course YMMV. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://lonesysadmin.net/2008/12/08/check-and-upgrade-vmware-tools/comment-page-1/#comment-75433</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 10 Dec 2008 05:13:56 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/?p=1692#comment-75433</guid>
		<description>I&#039;m with my frustrated friend above.  

As annoying as it is to have the VMs restart without warning, I have to wonder what they&#039;1l break with this patch.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with my frustrated friend above.  </p>
<p>As annoying as it is to have the VMs restart without warning, I have to wonder what they&#8217;1l break with this patch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frustrated but loyal</title>
		<link>http://lonesysadmin.net/2008/12/08/check-and-upgrade-vmware-tools/comment-page-1/#comment-75411</link>
		<dc:creator>Frustrated but loyal</dc:creator>
		<pubDate>Mon, 08 Dec 2008 18:50:19 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/?p=1692#comment-75411</guid>
		<description>I agree fully !

Update 2 had the time-bomb issue Update 3 has this VM restart issue.  I have a hard time keeping the momentum running at our site where virtualisation has been looked at as &quot;a nice toy but not ready for primetime&quot;.  How can i build confidence with &quot;patches&quot; that cause more isues than the issues themselves??  

Very frustrating ideed ! Please Vmware &quot;Get your patching act together&quot; I don&#039;t have multiple clusters to test all the patches on so I wait a reasonable time and then jump in, but now I&#039;m forced to wait longer and longer and patch less often for fear of these type of foul-ups.

Frustrated but still loyal.</description>
		<content:encoded><![CDATA[<p>I agree fully !</p>
<p>Update 2 had the time-bomb issue Update 3 has this VM restart issue.  I have a hard time keeping the momentum running at our site where virtualisation has been looked at as &#8220;a nice toy but not ready for primetime&#8221;.  How can i build confidence with &#8220;patches&#8221; that cause more isues than the issues themselves??  </p>
<p>Very frustrating ideed ! Please Vmware &#8220;Get your patching act together&#8221; I don&#8217;t have multiple clusters to test all the patches on so I wait a reasonable time and then jump in, but now I&#8217;m forced to wait longer and longer and patch less often for fear of these type of foul-ups.</p>
<p>Frustrated but still loyal.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
