<?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: Leaving ESX for Virtual Server?</title>
	<atom:link href="http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<pubDate>Thu, 08 Jan 2009 11:49:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32749</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Wed, 18 Jul 2007 19:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32749</guid>
		<description>Patrick,

Agreed--customers will and should choose the virtualization solution that works best for their environment and their situation.</description>
		<content:encoded><![CDATA[<p>Patrick,</p>
<p>Agreed&#8211;customers will and should choose the virtualization solution that works best for their environment and their situation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32748</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Wed, 18 Jul 2007 18:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32748</guid>
		<description>Scott - I'm in complete agreement with the 2nd to last paragraph of your blog post. And I'm not questioning VMware's installed base - their license revenue is now public information and speaks for itself. I wanted to provide examples of "important criteria" to two MS customers. The eval/selection criteria is often times much broader than technology or features, though technology/features tend to be most heavily weighted. In the end, there's a big virtualization market out there for customers, to choose amongst server virtualization, OS virtualization, application virtualization, presentation virtualization, storage, etc. Customers will choose what works best for their situation.</description>
		<content:encoded><![CDATA[<p>Scott - I&#8217;m in complete agreement with the 2nd to last paragraph of your blog post. And I&#8217;m not questioning VMware&#8217;s installed base - their license revenue is now public information and speaks for itself. I wanted to provide examples of &#8220;important criteria&#8221; to two MS customers. The eval/selection criteria is often times much broader than technology or features, though technology/features tend to be most heavily weighted. In the end, there&#8217;s a big virtualization market out there for customers, to choose amongst server virtualization, OS virtualization, application virtualization, presentation virtualization, storage, etc. Customers will choose what works best for their situation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32741</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Tue, 17 Jul 2007 23:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32741</guid>
		<description>Patrick,

In all honesty, would a Microsoft employee such as yourself be willing to admit that ESX Server has been found as the right choice by many organizations?  Over Virtual Server?

If you go back and read this posting, and read many of the comments, many of us pointed out that Virtual Server (like VMware Server) has its place, and it will be the right choice for some organizations.  However, ESX Server (instead of Virtual Server or VMware Server) will be the right choice for many organizations.  It is my personal opinion (an opinion that is apparently shared by many and backed up by numerous real-world implementations) that ESX Server offers a more robust, enterprise-class feature set that precludes direct comparison with Virtual Server.  There is no live migration (nor will there be in WSV--only "quick migration," which still involves downtime) and there is no equivalent to VMware Distributed Resource Scheduling (DRS) to help spread workloads evenly across all available physical hosts.

For many organizations, the (relatively) steep learning curve for ESX Server and VirtualCenter is outweighed by the advanced functionality.  For some organizations, as you've pointed out, Virtual Server's ease of use and similarity to existing Microsoft products and technologies will prove more beneficial.

NOTE:  Just for the record, as a former Microsoft-only engineer with NO significant Linux or UNIX experience, I didn't find the learning curve for ESX Server too steep to manage.  Anyone with prior UNIX or Linux experience will find it even easier, and the Windows-only VirtualCenter Server simplifies the management of the product even more.</description>
		<content:encoded><![CDATA[<p>Patrick,</p>
<p>In all honesty, would a Microsoft employee such as yourself be willing to admit that ESX Server has been found as the right choice by many organizations?  Over Virtual Server?</p>
<p>If you go back and read this posting, and read many of the comments, many of us pointed out that Virtual Server (like VMware Server) has its place, and it will be the right choice for some organizations.  However, ESX Server (instead of Virtual Server or VMware Server) will be the right choice for many organizations.  It is my personal opinion (an opinion that is apparently shared by many and backed up by numerous real-world implementations) that ESX Server offers a more robust, enterprise-class feature set that precludes direct comparison with Virtual Server.  There is no live migration (nor will there be in WSV&#8211;only &#8220;quick migration,&#8221; which still involves downtime) and there is no equivalent to VMware Distributed Resource Scheduling (DRS) to help spread workloads evenly across all available physical hosts.</p>
<p>For many organizations, the (relatively) steep learning curve for ESX Server and VirtualCenter is outweighed by the advanced functionality.  For some organizations, as you&#8217;ve pointed out, Virtual Server&#8217;s ease of use and similarity to existing Microsoft products and technologies will prove more beneficial.</p>
<p>NOTE:  Just for the record, as a former Microsoft-only engineer with NO significant Linux or UNIX experience, I didn&#8217;t find the learning curve for ESX Server too steep to manage.  Anyone with prior UNIX or Linux experience will find it even easier, and the Windows-only VirtualCenter Server simplifies the management of the product even more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32740</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Tue, 17 Jul 2007 21:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32740</guid>
		<description>Admittedly I'm behind the time here, having just found Scott's blog. I'll be sure to visit more often.

I work with MS and have been involved with Virtual Server since before it launched. Since then the reason for buying Virtual Server instead of other server virtualization software has changed primarily because the supply of virtualization software has changed. The selection criteria has lengthened compared to 3 years ago. Today customers's buying criteria includes: technology, integration, management (physical/virtual), skill set requirements, support, price, comprehensive roadmap, partners.

For Land O'Lakes, they compared ESX Server and Virtual Server against a weighted criteria of reliability (5), performance/scalability (4), supportability (3), fault tolerance (2), product/support costs (1). In the end, Virtual Server had a score of 71, and ESX Server scored 68. They also concluded that (their words, not mine): ESX Server has more functionality and less overhead; but, Virtual Server is mature/works, the roadmap meets future needs, pricing is attractive, stated support policy is more robust, their technical staff is more familiar with Microsoft technologies, and they believe virtualization will become part of the OS.

Citrix's IT dept had a similar evaluation. They looked at device support, features, roadmap, skills, implementation costs, operational savings, business relationship, management integration with current tools and support model. In the end, the cost to implement ESX Server was $331K+, whereas Virtual Server was $272K+. 

The two above examples come from a public presentation at Microsoft TechEd 2006 (June 06). More recent examples are here: http://www.microsoft.com/casestudies/search.aspx?ProTaxID=2273</description>
		<content:encoded><![CDATA[<p>Admittedly I&#8217;m behind the time here, having just found Scott&#8217;s blog. I&#8217;ll be sure to visit more often.</p>
<p>I work with MS and have been involved with Virtual Server since before it launched. Since then the reason for buying Virtual Server instead of other server virtualization software has changed primarily because the supply of virtualization software has changed. The selection criteria has lengthened compared to 3 years ago. Today customers&#8217;s buying criteria includes: technology, integration, management (physical/virtual), skill set requirements, support, price, comprehensive roadmap, partners.</p>
<p>For Land O&#8217;Lakes, they compared ESX Server and Virtual Server against a weighted criteria of reliability (5), performance/scalability (4), supportability (3), fault tolerance (2), product/support costs (1). In the end, Virtual Server had a score of 71, and ESX Server scored 68. They also concluded that (their words, not mine): ESX Server has more functionality and less overhead; but, Virtual Server is mature/works, the roadmap meets future needs, pricing is attractive, stated support policy is more robust, their technical staff is more familiar with Microsoft technologies, and they believe virtualization will become part of the OS.</p>
<p>Citrix&#8217;s IT dept had a similar evaluation. They looked at device support, features, roadmap, skills, implementation costs, operational savings, business relationship, management integration with current tools and support model. In the end, the cost to implement ESX Server was $331K+, whereas Virtual Server was $272K+. </p>
<p>The two above examples come from a public presentation at Microsoft TechEd 2006 (June 06). More recent examples are here: <a href="http://www.microsoft.com/casestudies/search.aspx?ProTaxID=2273" rel="nofollow">http://www.microsoft.com/casestudies/search.aspx?ProTaxID=2273</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curtis</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32452</link>
		<dc:creator>Curtis</dc:creator>
		<pubDate>Mon, 18 Jun 2007 13:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32452</guid>
		<description>I don't think that you can even compare Virtual Server to ESX. I agree that VMServer, Virtual Server, and ESX all have have different places in the grand scheme of things. VMServer or Virtual Server are great for small shops looking to dabble in virtualization. However I don't think that the article about switching from ESX to Virtual Server is even close to being accurate. Nothing holds a candle to ESX, it's not great for small shops that don't need high performance out of their virtualization, but anything else I cannot see why you choose anything over ESX. IMO the only thing that comes close to ESX is Virtual Iron.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think that you can even compare Virtual Server to ESX. I agree that VMServer, Virtual Server, and ESX all have have different places in the grand scheme of things. VMServer or Virtual Server are great for small shops looking to dabble in virtualization. However I don&#8217;t think that the article about switching from ESX to Virtual Server is even close to being accurate. Nothing holds a candle to ESX, it&#8217;s not great for small shops that don&#8217;t need high performance out of their virtualization, but anything else I cannot see why you choose anything over ESX. IMO the only thing that comes close to ESX is Virtual Iron.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32426</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Sun, 17 Jun 2007 03:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32426</guid>
		<description>I agree, and that is the point I was trying to make.  Virtual Server, VMware Server, and ESX Server all have their places within an overall virtualization solution--certain products are better in certain situations.  My experience has shown that ESX Server fits well in many, many environments, but that is not to say it will fit equally well in ALL cases, and there are going to be situations where Virtual Server, VMware Server, or perhaps even Xen will make more sense.  You can't go solely on cost, and you can't go solely on features.  You have to look at the final solution and take all these factors into consideration.</description>
		<content:encoded><![CDATA[<p>I agree, and that is the point I was trying to make.  Virtual Server, VMware Server, and ESX Server all have their places within an overall virtualization solution&#8211;certain products are better in certain situations.  My experience has shown that ESX Server fits well in many, many environments, but that is not to say it will fit equally well in ALL cases, and there are going to be situations where Virtual Server, VMware Server, or perhaps even Xen will make more sense.  You can&#8217;t go solely on cost, and you can&#8217;t go solely on features.  You have to look at the final solution and take all these factors into consideration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Marshall</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32425</link>
		<dc:creator>David Marshall</dc:creator>
		<pubDate>Sun, 17 Jun 2007 00:16:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32425</guid>
		<description>A few things... Virtual Server has its place.  Is it everything to everyone?  No.  Will it suffice for many organizations?  I think so.  Is it as robust and feature rich as VMware ESX Server?  No.  Of course not.  And I can't believe that anyone would say otherwise.  I'm sure even Microsoft would own up to that, after all, that's why they are working on Windows Server Virtualization.  

I have seen ESX Server PSOD, mostly because of hardware issues... but it has crashed on me for other reasons of heavy usage.  Again, it crashes few and far between, but it certainly isn't bullet proof.

VMware Server is free as well, and again, nowhere near the stability or resource allocation of ESX Server.  Free... yes.  I would also argue that it doesn't scale as well as Virtual Server either.  If you are running a few virtual machines on a server, VMware Server is fine.  When you start loading it up, the performance drops faster than the other two platforms.

So it all comes back to what are you trying to do within your organization.  Outside of cost, what are you hoping to accomplish with virtualization?</description>
		<content:encoded><![CDATA[<p>A few things&#8230; Virtual Server has its place.  Is it everything to everyone?  No.  Will it suffice for many organizations?  I think so.  Is it as robust and feature rich as VMware ESX Server?  No.  Of course not.  And I can&#8217;t believe that anyone would say otherwise.  I&#8217;m sure even Microsoft would own up to that, after all, that&#8217;s why they are working on Windows Server Virtualization.  </p>
<p>I have seen ESX Server PSOD, mostly because of hardware issues&#8230; but it has crashed on me for other reasons of heavy usage.  Again, it crashes few and far between, but it certainly isn&#8217;t bullet proof.</p>
<p>VMware Server is free as well, and again, nowhere near the stability or resource allocation of ESX Server.  Free&#8230; yes.  I would also argue that it doesn&#8217;t scale as well as Virtual Server either.  If you are running a few virtual machines on a server, VMware Server is fine.  When you start loading it up, the performance drops faster than the other two platforms.</p>
<p>So it all comes back to what are you trying to do within your organization.  Outside of cost, what are you hoping to accomplish with virtualization?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denny</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32412</link>
		<dc:creator>Denny</dc:creator>
		<pubDate>Fri, 15 Jun 2007 14:40:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32412</guid>
		<description>I wonder if they tried VMware Server.  It is free and is much more functional than Virtual Server.</description>
		<content:encoded><![CDATA[<p>I wonder if they tried VMware Server.  It is free and is much more functional than Virtual Server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32411</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Fri, 15 Jun 2007 11:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32411</guid>
		<description>The only PSODs I've seen have always been due to hardware failure.  Definitely better track record than Windows!</description>
		<content:encoded><![CDATA[<p>The only PSODs I&#8217;ve seen have always been due to hardware failure.  Definitely better track record than Windows!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMzare</title>
		<link>http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32410</link>
		<dc:creator>VMzare</dc:creator>
		<pubDate>Fri, 15 Jun 2007 08:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/06/15/leaving-esx-for-virtual-server/#comment-32410</guid>
		<description>I agree with you fully, I wouldn't even go further and compare these products. ESX is enterprize level product and It truly means Enterprize. Load,capacity and above all Stability. Above kind of innovation gone into GSX,ESX family will never let the product down. I've yet to see any ESX host PSOD because of VMKernel.</description>
		<content:encoded><![CDATA[<p>I agree with you fully, I wouldn&#8217;t even go further and compare these products. ESX is enterprize level product and It truly means Enterprize. Load,capacity and above all Stability. Above kind of innovation gone into GSX,ESX family will never let the product down. I&#8217;ve yet to see any ESX host PSOD because of VMKernel.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
