<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Support for Virtualized OS/Applications &#8211; an Open Debate..</title>
	<atom:link href="http://vinf.net/2008/02/21/support-for-virtualized-osapplications-an-open-debate/feed/" rel="self" type="application/rss+xml" />
	<link>http://vinf.net/2008/02/21/support-for-virtualized-osapplications-an-open-debate/</link>
	<description>My ramblings on the stuff that holds it all together</description>
	<lastBuildDate>Tue, 24 Apr 2012 00:23:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: vinf</title>
		<link>http://vinf.net/2008/02/21/support-for-virtualized-osapplications-an-open-debate/#comment-165</link>
		<dc:creator><![CDATA[vinf]]></dc:creator>
		<pubDate>Tue, 03 Jun 2008 15:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2008/02/21/support-for-virtualized-osapplications-an-open-debate/#comment-165</guid>
		<description><![CDATA[by way of a follow-up useful article at vmware.com here;

http://www.vmware.com/support/policies/ms_support_statement.html

Interesting to see the extra options for customers who OEM their vmware software with services.. they give end-end support.

thanks to Scott
http://blog.scottlowe.org/2008/05/31/virtualization-short-take-9/]]></description>
		<content:encoded><![CDATA[<p>by way of a follow-up useful article at vmware.com here;</p>
<p><a href="http://www.vmware.com/support/policies/ms_support_statement.html" rel="nofollow">http://www.vmware.com/support/policies/ms_support_statement.html</a></p>
<p>Interesting to see the extra options for customers who OEM their vmware software with services.. they give end-end support.</p>
<p>thanks to Scott<br />
<a href="http://blog.scottlowe.org/2008/05/31/virtualization-short-take-9/" rel="nofollow">http://blog.scottlowe.org/2008/05/31/virtualization-short-take-9/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Rogers</title>
		<link>http://vinf.net/2008/02/21/support-for-virtualized-osapplications-an-open-debate/#comment-71</link>
		<dc:creator><![CDATA[Jay Rogers]]></dc:creator>
		<pubDate>Wed, 05 Mar 2008 18:49:27 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2008/02/21/support-for-virtualized-osapplications-an-open-debate/#comment-71</guid>
		<description><![CDATA[EVERYONE in the industry is in agreement virtualization is going to be the way of the future (and has been the way for some for many years already). Otherwise I don&#039;t think Microsoft would be spending so much effort on Hyper-V. 

It just seems Microsoft could be fair to all those doing virtualization (especially VMware customers who have really brought this into the datacenters over the last several years and caused most of the interest in the first place). 

Could Microsoft not come up with some legal way of saying &quot;once we suspect an issue is caused by virtualization the machine will need to be reproduced on physical for support&quot; (there are many tools out there now to help with this)..but NOT limit the support to many of the popular Microsoft applications that are known to work in virtual fine already. (Heck, at VMworld Europe they just showed how you could exceed what normally has been possible with Exchange in a virtual environment).

Or will Microsoft release the great Hyper-V but then say but we don&#039;t trust you running Exchange, and this and that in hyper-v? Or will they simply suddenly find the time to test all Microsoft applications in Hyper-V (and maybe XenServer..IE Citrix due to the agreements) and certify them ok for those but not for other hypervisors?

Microsoft has also lately warmed up to open source and I think with the virtual revolution has the chance to help us all work in the virtual world we all know is better...even if we don&#039;t all drive the same car (ie. hypervisor).]]></description>
		<content:encoded><![CDATA[<p>EVERYONE in the industry is in agreement virtualization is going to be the way of the future (and has been the way for some for many years already). Otherwise I don&#8217;t think Microsoft would be spending so much effort on Hyper-V. </p>
<p>It just seems Microsoft could be fair to all those doing virtualization (especially VMware customers who have really brought this into the datacenters over the last several years and caused most of the interest in the first place). </p>
<p>Could Microsoft not come up with some legal way of saying &#8220;once we suspect an issue is caused by virtualization the machine will need to be reproduced on physical for support&#8221; (there are many tools out there now to help with this)..but NOT limit the support to many of the popular Microsoft applications that are known to work in virtual fine already. (Heck, at VMworld Europe they just showed how you could exceed what normally has been possible with Exchange in a virtual environment).</p>
<p>Or will Microsoft release the great Hyper-V but then say but we don&#8217;t trust you running Exchange, and this and that in hyper-v? Or will they simply suddenly find the time to test all Microsoft applications in Hyper-V (and maybe XenServer..IE Citrix due to the agreements) and certify them ok for those but not for other hypervisors?</p>
<p>Microsoft has also lately warmed up to open source and I think with the virtual revolution has the chance to help us all work in the virtual world we all know is better&#8230;even if we don&#8217;t all drive the same car (ie. hypervisor).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virtualization Short Take #3 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</title>
		<link>http://vinf.net/2008/02/21/support-for-virtualized-osapplications-an-open-debate/#comment-69</link>
		<dc:creator><![CDATA[Virtualization Short Take #3 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers]]></dc:creator>
		<pubDate>Tue, 04 Mar 2008 03:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2008/02/21/support-for-virtualized-osapplications-an-open-debate/#comment-69</guid>
		<description><![CDATA[[...] of vendor support, Simon Gallagher at vinf.net has started an open discussion of vendor support for virtualization. This is truly a difficult sticking point for many organizations. Visionary [...]]]></description>
		<content:encoded><![CDATA[<p>[...] of vendor support, Simon Gallagher at vinf.net has started an open discussion of vendor support for virtualization. This is truly a difficult sticking point for many organizations. Visionary [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vinf</title>
		<link>http://vinf.net/2008/02/21/support-for-virtualized-osapplications-an-open-debate/#comment-50</link>
		<dc:creator><![CDATA[vinf]]></dc:creator>
		<pubDate>Tue, 26 Feb 2008 14:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://vinf.wordpress.com/2008/02/21/support-for-virtualized-osapplications-an-open-debate/#comment-50</guid>
		<description><![CDATA[Have had some correspondence from Ben with regards to this post(aka virtual PC guy at Microsoft)... useful.

the MS/legal angle makes things a bit clearer.. how do you handle this with your production VM platforms?

-----8&lt;--------

Hi,

To give you some perspective on Microsoft&#039;s support policy of software under virtualization there are two key things that you need to understand:

1) At Microsoft it is mostly up to the individual product teams to drive their own supports statements.  This is why you see different products offering different levels of support inside of virtualization.

2) For Microsoft to say that a product is &quot;supported&quot; on a virtualization platform it means that we are placing a legal liability on ourselves to be able to guarantee to customers that our software will run there and that we will correct any issues encountered on that platform.  As such the &quot;it runs okay when I try it&quot; statement that is made in your blog is simply not sufficient.  Microsoft product teams are not comfortable making statements of support unless that have conducted full, extensive testing of their product on said configurations.  Given that for many product teams this can mean an investment of months of test time - they need to prioritize this work against other features that their customers are asking for.

Please feel free to ask me for further clarification if you need it.

Cheers,
Ben

Windows Virtualization Program Manager.
http://blogs.msdn.com/Virtual_PC_Guy]]></description>
		<content:encoded><![CDATA[<p>Have had some correspondence from Ben with regards to this post(aka virtual PC guy at Microsoft)&#8230; useful.</p>
<p>the MS/legal angle makes things a bit clearer.. how do you handle this with your production VM platforms?</p>
<p>&#8212;&#8211;8&lt;&#8212;&#8212;&#8211;</p>
<p>Hi,</p>
<p>To give you some perspective on Microsoft&#8217;s support policy of software under virtualization there are two key things that you need to understand:</p>
<p>1) At Microsoft it is mostly up to the individual product teams to drive their own supports statements.  This is why you see different products offering different levels of support inside of virtualization.</p>
<p>2) For Microsoft to say that a product is &#8220;supported&#8221; on a virtualization platform it means that we are placing a legal liability on ourselves to be able to guarantee to customers that our software will run there and that we will correct any issues encountered on that platform.  As such the &#8220;it runs okay when I try it&#8221; statement that is made in your blog is simply not sufficient.  Microsoft product teams are not comfortable making statements of support unless that have conducted full, extensive testing of their product on said configurations.  Given that for many product teams this can mean an investment of months of test time &#8211; they need to prioritize this work against other features that their customers are asking for.</p>
<p>Please feel free to ask me for further clarification if you need it.</p>
<p>Cheers,<br />
Ben</p>
<p>Windows Virtualization Program Manager.<br />
<a href="http://blogs.msdn.com/Virtual_PC_Guy" rel="nofollow">http://blogs.msdn.com/Virtual_PC_Guy</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

