<?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: Hyper-V Architectural Issue</title>
	<atom:link href="http://blog.scottlowe.org/2007/12/31/hyper-v-architectural-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2007/12/31/hyper-v-architectural-issue/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<pubDate>Fri, 21 Nov 2008 14:28:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: bert</title>
		<link>http://blog.scottlowe.org/2007/12/31/hyper-v-architectural-issue/#comment-35266</link>
		<dc:creator>bert</dc:creator>
		<pubDate>Thu, 31 Jan 2008 14:21:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/12/31/hyper-v-architectural-issue/#comment-35266</guid>
		<description>A disk filter driver, that would mean that it is a performance issue if the correct VM tools are not installed or not functioning correctly in the guest ? I agree that installing the necessary drivers is very important, but why not take the short way round ? Especially people testing previously unsupported guest OSes might not have the opportunity to install your drivers in their guest.</description>
		<content:encoded><![CDATA[<p>A disk filter driver, that would mean that it is a performance issue if the correct VM tools are not installed or not functioning correctly in the guest ? I agree that installing the necessary drivers is very important, but why not take the short way round ? Especially people testing previously unsupported guest OSes might not have the opportunity to install your drivers in their guest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2007/12/31/hyper-v-architectural-issue/#comment-34862</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Mon, 31 Dec 2007 22:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/12/31/hyper-v-architectural-issue/#comment-34862</guid>
		<description>Ben,

Thanks for the link; that's important information to have. I've updated the article to reflect the information in your comment.

Thanks for reading!</description>
		<content:encoded><![CDATA[<p>Ben,</p>
<p>Thanks for the link; that&#8217;s important information to have. I&#8217;ve updated the article to reflect the information in your comment.</p>
<p>Thanks for reading!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Armstrong [MSFT]</title>
		<link>http://blog.scottlowe.org/2007/12/31/hyper-v-architectural-issue/#comment-34858</link>
		<dc:creator>Ben Armstrong [MSFT]</dc:creator>
		<pubDate>Mon, 31 Dec 2007 19:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2007/12/31/hyper-v-architectural-issue/#comment-34858</guid>
		<description>Actually, we load a disk filter driver on all IDE disks which allows them to have exactly the same performance characteristics as SCSI disks.  This means that from a performance point of view this is a non-issue.  For more details checkout: http://blogs.technet.com/jhoward/archive/2007/10/04/boot-from-scsi-in-virtual-server-vs-boot-from-ide-in-windows-server-virtualization.aspx

Cheers,
Ben</description>
		<content:encoded><![CDATA[<p>Actually, we load a disk filter driver on all IDE disks which allows them to have exactly the same performance characteristics as SCSI disks.  This means that from a performance point of view this is a non-issue.  For more details checkout: <a href="http://blogs.technet.com/jhoward/archive/2007/10/04/boot-from-scsi-in-virtual-server-vs-boot-from-ide-in-windows-server-virtualization.aspx" rel="nofollow">http://blogs.technet.com/jhoward/archive/2007/10/04/boot-from-scsi-in-virtual-server-vs-boot-from-ide-in-windows-server-virtualization.aspx</a></p>
<p>Cheers,<br />
Ben</p>
]]></content:encoded>
	</item>
</channel>
</rss>
