<?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: August 12 BUG in ESX 3.5 Update 2</title>
	<atom:link href="http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Wed, 17 Mar 2010 10:29:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: DeSchans.org &#187; ESX Update 2 internal error</title>
		<link>http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/comment-page-1/#comment-2508</link>
		<dc:creator>DeSchans.org &#187; ESX Update 2 internal error</dc:creator>
		<pubDate>Tue, 19 May 2009 20:36:03 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=573#comment-2508</guid>
		<description>[...] http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/" rel="nofollow">http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/comment-page-1/#comment-1000</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Wed, 13 Aug 2008 11:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=573#comment-1000</guid>
		<description>Lukas,

No offense taken. I am a VMware user and advocate and do feel this pain too. I am also open to and constantly evaluating Hyper-V, Citrix Xenserver, Sun xVM, KVM, etc. In some ways I&#039;m counting on guys like you to keep me in the &quot;know&quot; about the alternatives. 

Thanks for reading VM /ETC!</description>
		<content:encoded><![CDATA[<p>Lukas,</p>
<p>No offense taken. I am a VMware user and advocate and do feel this pain too. I am also open to and constantly evaluating Hyper-V, Citrix Xenserver, Sun xVM, KVM, etc. In some ways I&#8217;m counting on guys like you to keep me in the &#8220;know&#8221; about the alternatives. </p>
<p>Thanks for reading VM /ETC!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/comment-page-1/#comment-999</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Wed, 13 Aug 2008 11:06:24 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=573#comment-999</guid>
		<description>Lukas,

True this has been an embarrassing and humbling experience for VMware, but to suggest that Hyper-V is a superior alternative because of a gap in VMware\&#039;s regression testing is a stretch in my opinion.

There will no doubt be irate customers that switch because of emotion. That\&#039;s different than recognizing a technical or business advantage. It will be interesting to see where these customers are at in 6 months.

Maybe VMware has spoiled everyone by having such a good track record with patches and upgrades to date, but now I think that these same irate customers need to look in the mirror and realize they also examine their own change control process for production systems as well.</description>
		<content:encoded><![CDATA[<p>Lukas,</p>
<p>True this has been an embarrassing and humbling experience for VMware, but to suggest that Hyper-V is a superior alternative because of a gap in VMware\&#8217;s regression testing is a stretch in my opinion.</p>
<p>There will no doubt be irate customers that switch because of emotion. That\&#8217;s different than recognizing a technical or business advantage. It will be interesting to see where these customers are at in 6 months.</p>
<p>Maybe VMware has spoiled everyone by having such a good track record with patches and upgrades to date, but now I think that these same irate customers need to look in the mirror and realize they also examine their own change control process for production systems as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lukas Beeler</title>
		<link>http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/comment-page-1/#comment-998</link>
		<dc:creator>Lukas Beeler</dc:creator>
		<pubDate>Wed, 13 Aug 2008 06:10:16 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=573#comment-998</guid>
		<description>And by that i don&#039;t mean you or anyone else in particular.</description>
		<content:encoded><![CDATA[<p>And by that i don&#8217;t mean you or anyone else in particular.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lukas Beeler</title>
		<link>http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/comment-page-1/#comment-997</link>
		<dc:creator>Lukas Beeler</dc:creator>
		<pubDate>Wed, 13 Aug 2008 06:05:59 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=573#comment-997</guid>
		<description>Rich, 

As i said, it just shows that VMware is not perfect and just cooking with water. It&#039;s all about the &quot;high and mighty&quot; attitude of VMware users ;)</description>
		<content:encoded><![CDATA[<p>Rich, </p>
<p>As i said, it just shows that VMware is not perfect and just cooking with water. It&#8217;s all about the &#8220;high and mighty&#8221; attitude of VMware users <img src='http://vmetc.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/comment-page-1/#comment-990</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Tue, 12 Aug 2008 20:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=573#comment-990</guid>
		<description>Lukas,

This was a mistake on the part of the ESX product team in the distribution of ESX 3.5 U2. A developmental time bomb was not removed in the hurry to get it to market.  Of course, MS is always able to smoothly distribute products that are completely ready for release, right? Do you really want to start that discussion?</description>
		<content:encoded><![CDATA[<p>Lukas,</p>
<p>This was a mistake on the part of the ESX product team in the distribution of ESX 3.5 U2. A developmental time bomb was not removed in the hurry to get it to market.  Of course, MS is always able to smoothly distribute products that are completely ready for release, right? Do you really want to start that discussion?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lukas Beeler</title>
		<link>http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/comment-page-1/#comment-989</link>
		<dc:creator>Lukas Beeler</dc:creator>
		<pubDate>Tue, 12 Aug 2008 20:29:40 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=573#comment-989</guid>
		<description>While it looks like a simple human error (timebomb from betas left in final product), i&#039;ll still use this to piss of all the guys that said Hyper-V isn&#039;t &quot;Enterprise&quot; ready.

It clearly shows that even VMware is still cooking with water.</description>
		<content:encoded><![CDATA[<p>While it looks like a simple human error (timebomb from betas left in final product), i&#8217;ll still use this to piss of all the guys that said Hyper-V isn&#8217;t &#8220;Enterprise&#8221; ready.</p>
<p>It clearly shows that even VMware is still cooking with water.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WARNING! August 12 bug in ESX 3.5 update 2 &#171; Michael Ellerbeck</title>
		<link>http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/comment-page-1/#comment-987</link>
		<dc:creator>WARNING! August 12 bug in ESX 3.5 update 2 &#171; Michael Ellerbeck</dc:creator>
		<pubDate>Tue, 12 Aug 2008 15:33:42 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=573#comment-987</guid>
		<description>[...] WARNING! August 12 bug in ESX 3.5 update&#160;2  Posted on August 12, 2008 by mellerbeck   http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/ [...]</description>
		<content:encoded><![CDATA[<p>[...] WARNING! August 12 bug in ESX 3.5 update&nbsp;2  Posted on August 12, 2008 by mellerbeck   <a href="http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/" rel="nofollow">http://vmetc.com/2008/08/11/august-12-bug-in-esx-35-update-2/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
