<?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: Desktop Virtualization Sizing &amp; Scoping</title>
	<atom:link href="http://www.latogalabs.com/2009/03/desktop-virtualization-sizing-scoping/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.latogalabs.com/2009/03/desktop-virtualization-sizing-scoping/</link>
	<description>Virtualization, Cloud Computing, Technology of Business &#38; Business of Technology</description>
	<lastBuildDate>Wed, 24 Aug 2011 12:02:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: latoga</title>
		<link>http://www.latogalabs.com/2009/03/desktop-virtualization-sizing-scoping/comment-page-1/#comment-234</link>
		<dc:creator>latoga</dc:creator>
		<pubDate>Tue, 10 Mar 2009 05:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=499#comment-234</guid>
		<description>I completely agree with you that per core pricing is the only thing that makes sense for the hypervisor and related management technology layers.  It still kills me that so many ISVs don&#039;t understand how to license appropriately for virtualized environments (both the big ones that always come to mind as well as small ones).  But, as one VP of Data Center Strategy commented in a recent meeting &quot;If they don&#039;t support it running in a VM, good for me!  Because I&#039;ll run it in a VM, not pay support and save myself a bunch on maintenance.&quot;</description>
		<content:encoded><![CDATA[<p>I completely agree with you that per core pricing is the only thing that makes sense for the hypervisor and related management technology layers.  It still kills me that so many ISVs don&#8217;t understand how to license appropriately for virtualized environments (both the big ones that always come to mind as well as small ones).  But, as one VP of Data Center Strategy commented in a recent meeting &#8220;If they don&#8217;t support it running in a VM, good for me!  Because I&#8217;ll run it in a VM, not pay support and save myself a bunch on maintenance.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Wolf</title>
		<link>http://www.latogalabs.com/2009/03/desktop-virtualization-sizing-scoping/comment-page-1/#comment-232</link>
		<dc:creator>Chris Wolf</dc:creator>
		<pubDate>Mon, 09 Mar 2009 20:09:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.latogalabs.com/?p=499#comment-232</guid>
		<description>Good post, Greg. I agree with your comments on sizing. In my post, I had made assumptions on server platforms and should have stated them explicitly. I was assuming 8-16 cores in the 30-60 desktop VM consolidation density range. VMs per core is abosolutely how density should be judged. This is also why I think eventually we&#039;ll see hypervisor platform licensing based on physical cores, since it&#039;s the easiest and most accurate way to way the value of a virtualization software license. To be clear, I&#039;m only condoning this model for the software that runs on the metail (i.e., the hypervisor and supporting services such as high availability). Software running inside VMs should have absolutely no ties to the physical hardware.</description>
		<content:encoded><![CDATA[<p>Good post, Greg. I agree with your comments on sizing. In my post, I had made assumptions on server platforms and should have stated them explicitly. I was assuming 8-16 cores in the 30-60 desktop VM consolidation density range. VMs per core is abosolutely how density should be judged. This is also why I think eventually we&#8217;ll see hypervisor platform licensing based on physical cores, since it&#8217;s the easiest and most accurate way to way the value of a virtualization software license. To be clear, I&#8217;m only condoning this model for the software that runs on the metail (i.e., the hypervisor and supporting services such as high availability). Software running inside VMs should have absolutely no ties to the physical hardware.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

