<?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"
	>
<channel>
	<title>Comments on: Major ESX bug plagues thousands of VMware customers</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/server-virtualization/major-esx-bug-plagues-thousands-of-vmware-customers/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/server-virtualization/major-esx-bug-plagues-thousands-of-vmware-customers/</link>
	<description>A SearchServerVirtualization.com blog</description>
	<pubDate>Thu, 26 Nov 2009 22:56:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Eric Siebert</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/major-esx-bug-plagues-thousands-of-vmware-customers/#comment-1494</link>
		<dc:creator>Eric Siebert</dc:creator>
		<pubDate>Thu, 14 Aug 2008 16:37:57 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/08/12/major-esx-bug-plagues-thousands-of-vmware-customers/#comment-1494</guid>
		<description>Hi Rick, 

VMware was exploring various ways for deploying the patch without shutting down VMs on the host but was never able to come up with one. In order to install the patch you need to shutdown or vMotion the VMs to another host, put the host in maintenance mode and install the express patch that was released. There is sort of a workaround to get vMotion to work by changing the clock on one host that I mentioned in the below thread.

http://itknowledgeexchange.techtarget.com/virtualization-pro/vmware-releases-emergency-patch-for-esx-35-update-2-bug/</description>
		<content:encoded><![CDATA[<p>Hi Rick, </p>
<p>VMware was exploring various ways for deploying the patch without shutting down VMs on the host but was never able to come up with one. In order to install the patch you need to shutdown or vMotion the VMs to another host, put the host in maintenance mode and install the express patch that was released. There is sort of a workaround to get vMotion to work by changing the clock on one host that I mentioned in the below thread.<br />
&nbsp;&lt;a href="http://itknowledgeexchange.techtarget.com/virtualization-pro/vmware-releases-emergency-patch-for-esx-35-update-2-bug/" title="http://itknowledgeexchange.techtarget.com/virtualization-pro/vmware-releases-emergency-patch-for-esx-35-update-2-bug/" target="_blank"&gt;http://itknowledgeexchange.techtarget.co&#8230;&lt;/a&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gilson Soares</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/major-esx-bug-plagues-thousands-of-vmware-customers/#comment-1493</link>
		<dc:creator>Gilson Soares</dc:creator>
		<pubDate>Wed, 13 Aug 2008 03:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/08/12/major-esx-bug-plagues-thousands-of-vmware-customers/#comment-1493</guid>
		<description>Patch Available:
http://kb.vmware.com/selfservice/dynamickc.do?externalId=1006721&#38;sliceId=1&#38;command=show&#38;forward=nonthreadedKC&#38;kcId=1006721</description>
		<content:encoded><![CDATA[<p>Patch Available:&nbsp;&lt;a href="http://kb.vmware.com/selfservice/dynamickc.do?externalId=1006721&amp;sliceId=1&amp;command=show&amp;forward=nonthreadedKC&amp;kcId=1006721" title="http://kb.vmware.com/selfservice/dynamickc.do?externalId=1006721&amp;sliceId=1&amp;command=show&amp;forward=nonthreadedKC&amp;kcId=1006721" target="_blank"&gt;http://kb.vmware.com/selfservice/dynamic&#8230;&lt;/a&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Vanover</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/major-esx-bug-plagues-thousands-of-vmware-customers/#comment-1492</link>
		<dc:creator>Rick Vanover</dc:creator>
		<pubDate>Tue, 12 Aug 2008 18:22:47 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/08/12/major-esx-bug-plagues-thousands-of-vmware-customers/#comment-1492</guid>
		<description>I am very curious what the resolution how the resolution will work for existing installations of ESX 3.5 U2 / VC 2.5 U2. Meaning - will they be able to correct it so that they can immediately enable DRS and HA - or will the shutdown of the VMs be required?</description>
		<content:encoded><![CDATA[<p>I am very curious what the resolution how the resolution will work for existing installations of ESX 3.5 U2 / VC 2.5 U2. Meaning - will they be able to correct it so that they can immediately enable DRS and HA - or will the shutdown of the VMs be required?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sexton Lovecraft</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/major-esx-bug-plagues-thousands-of-vmware-customers/#comment-1491</link>
		<dc:creator>Sexton Lovecraft</dc:creator>
		<pubDate>Tue, 12 Aug 2008 18:19:09 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2008/08/12/major-esx-bug-plagues-thousands-of-vmware-customers/#comment-1491</guid>
		<description>Shocking. VMware competitors could do no better with industrial espionage. Unless they just did.</description>
		<content:encoded><![CDATA[<p>Shocking. VMware competitors could do no better with industrial espionage. Unless they just did.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->