<?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: Isolation mode on VMware ESX servers</title>
	<atom:link href="http://rickardandersson.com/isolation-mode-on-vmware-esx-servers/feed" rel="self" type="application/rss+xml" />
	<link>http://rickardandersson.com/isolation-mode-on-vmware-esx-servers</link>
	<description>The general consensus among clients is that they are your only client.</description>
	<lastBuildDate>Wed, 28 Jul 2010 02:42:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0-RC2-15182</generator>
	<item>
		<title>By: Paul</title>
		<link>http://rickardandersson.com/isolation-mode-on-vmware-esx-servers#comment-58310</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 31 Dec 2009 21:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://rickardandersson.com/?p=276#comment-58310</guid>
		<description>Good news, probably.  VMWare KB article 1003165 dated 8-Dec-09 says &quot;For VMware VirtualCenter 2.5.x and later, the default isolation response is Leave VM Powered ON.&quot;</description>
		<content:encoded><![CDATA[<p>Good news, probably.  VMWare KB article 1003165 dated 8-Dec-09 says &#8220;For VMware VirtualCenter 2.5.x and later, the default isolation response is Leave VM Powered ON.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Biju</title>
		<link>http://rickardandersson.com/isolation-mode-on-vmware-esx-servers#comment-41606</link>
		<dc:creator>Biju</dc:creator>
		<pubDate>Thu, 05 Mar 2009 11:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://rickardandersson.com/?p=276#comment-41606</guid>
		<description>Yes, Theo is right. In Isolation mode the ESX server will shut down all the VM&#039;s to prevent split brain scenario. That is One ESX Host won&#039;t know what the Other ESX host in the cluster is doing with its VM.

Hence it shuts down VM (not gracefully though). This will ensure that the VM files are unlocked from the VMFS and can be started from other ESX server.</description>
		<content:encoded><![CDATA[<p>Yes, Theo is right. In Isolation mode the ESX server will shut down all the VM&#8217;s to prevent split brain scenario. That is One ESX Host won&#8217;t know what the Other ESX host in the cluster is doing with its VM.</p>
<p>Hence it shuts down VM (not gracefully though). This will ensure that the VM files are unlocked from the VMFS and can be started from other ESX server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rickard</title>
		<link>http://rickardandersson.com/isolation-mode-on-vmware-esx-servers#comment-39886</link>
		<dc:creator>Rickard</dc:creator>
		<pubDate>Thu, 26 Feb 2009 21:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://rickardandersson.com/?p=276#comment-39886</guid>
		<description>You have a point there. The scenario would be similar to when a host has failed.

David: Hohoho :)</description>
		<content:encoded><![CDATA[<p>You have a point there. The scenario would be similar to when a host has failed.</p>
<p>David: Hohoho :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theo</title>
		<link>http://rickardandersson.com/isolation-mode-on-vmware-esx-servers#comment-39873</link>
		<dc:creator>Theo</dc:creator>
		<pubDate>Thu, 26 Feb 2009 20:10:58 +0000</pubDate>
		<guid isPermaLink="false">http://rickardandersson.com/?p=276#comment-39873</guid>
		<description>The single isolated vmware host has no way to tell if the same thing happened to the other servers so it seems very logical.

The only thing the vmware host can safely assume is that the other vmware hosts in the cluster will mark the hosts as failed and start the guests that were running on the failed vmware host.</description>
		<content:encoded><![CDATA[<p>The single isolated vmware host has no way to tell if the same thing happened to the other servers so it seems very logical.</p>
<p>The only thing the vmware host can safely assume is that the other vmware hosts in the cluster will mark the hosts as failed and start the guests that were running on the failed vmware host.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://rickardandersson.com/isolation-mode-on-vmware-esx-servers#comment-39760</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 26 Feb 2009 11:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://rickardandersson.com/?p=276#comment-39760</guid>
		<description>&quot;I’m still not sure why the default is to shut down the machines. I mean, won’t forcibly shutting down a virtual machine potentially cause more problems than letting it run without a network connection?&quot;

Oh yes. Definitely. No doubt at all in my mind.

/David</description>
		<content:encoded><![CDATA[<p>&#8220;I’m still not sure why the default is to shut down the machines. I mean, won’t forcibly shutting down a virtual machine potentially cause more problems than letting it run without a network connection?&#8221;</p>
<p>Oh yes. Definitely. No doubt at all in my mind.</p>
<p>/David</p>
]]></content:encoded>
	</item>
</channel>
</rss>
