<?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:go='http://ns.gigaom.com/'
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: Next Up: I/O Virtualization?</title>
	<atom:link href="http://gigaom.com/2008/02/28/next-up-io-virtualization/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 12:44:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Virtualized I/O Takes Cloud Computing to the Next Level</title>
		<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/#comment-194919</link>
		<dc:creator><![CDATA[Virtualized I/O Takes Cloud Computing to the Next Level]]></dc:creator>
		<pubDate>Mon, 20 Jul 2009 14:53:15 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11654#comment-194919</guid>
		<description><![CDATA[[...] reliability (that means it can go down 53 minutes each year), said today it will save $1 million by virtualizing its network and will spend 50 percent less to deliver its high reliability cloud. The company has installed [...]]]></description>
		<content:encoded><![CDATA[<p>[...] reliability (that means it can go down 53 minutes each year), said today it will save $1 million by virtualizing its network and will spend 50 percent less to deliver its high reliability cloud. The company has installed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Technical blogs with pictures and videos &#187; Xsigo Raises Money for Virtual I/O</title>
		<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/#comment-194918</link>
		<dc:creator><![CDATA[Technical blogs with pictures and videos &#187; Xsigo Raises Money for Virtual I/O]]></dc:creator>
		<pubDate>Thu, 04 Jun 2009 01:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11654#comment-194918</guid>
		<description><![CDATA[[...] Byers, Greylock Partners, Khosla Ventures and North Bridge Venture Partners to support sales of its I/O virtualization appliance. Several filings submitted to the California Department of Securities show that back in [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Byers, Greylock Partners, Khosla Ventures and North Bridge Venture Partners to support sales of its I/O virtualization appliance. Several filings submitted to the California Department of Securities show that back in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xsigo Raises Money for Virtual I/O</title>
		<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/#comment-194917</link>
		<dc:creator><![CDATA[Xsigo Raises Money for Virtual I/O]]></dc:creator>
		<pubDate>Wed, 03 Jun 2009 18:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11654#comment-194917</guid>
		<description><![CDATA[[...] Byers, Greylock Partners, Khosla Ventures and North Bridge Venture Partners to support sales of its I/O virtualization appliance. Several filings submitted to the California Department of Securities show that back in [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Byers, Greylock Partners, Khosla Ventures and North Bridge Venture Partners to support sales of its I/O virtualization appliance. Several filings submitted to the California Department of Securities show that back in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kennyo</title>
		<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/#comment-194916</link>
		<dc:creator><![CDATA[Kennyo]]></dc:creator>
		<pubDate>Sat, 01 Mar 2008 17:52:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11654#comment-194916</guid>
		<description><![CDATA[&lt;p&gt;The very cool part of I/O virtualization isn&#039;t the fact that it interoperates with all of the other (redundant?) transfer mechanisms, or that it makes it &quot;easy to connect the VM&quot; to different resources... although that&#039;s part of it.&lt;/p&gt;

&lt;p&gt;The thing that&#039;s valueable is that when one provisions a piece of software to a piece of hardware (whether-or-not it&#039;s been virtualized) one can provision a &quot;virtual NIC&quot; at the same time.&lt;/p&gt;

&lt;p&gt;So picture the future: software, I/O, and presumably storage, can be allocated on-the-fly as compute demands dictate. Very much of an automated &quot;cloud&quot; scenario.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>The very cool part of I/O virtualization isn&#8217;t the fact that it interoperates with all of the other (redundant?) transfer mechanisms, or that it makes it &#8220;easy to connect the VM&#8221; to different resources&#8230; although that&#8217;s part of it.</p>
<p>The thing that&#8217;s valueable is that when one provisions a piece of software to a piece of hardware (whether-or-not it&#8217;s been virtualized) one can provision a &#8220;virtual NIC&#8221; at the same time.</p>
<p>So picture the future: software, I/O, and presumably storage, can be allocated on-the-fly as compute demands dictate. Very much of an automated &#8220;cloud&#8221; scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/#comment-194915</link>
		<dc:creator><![CDATA[Richard]]></dc:creator>
		<pubDate>Sat, 01 Mar 2008 06:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11654#comment-194915</guid>
		<description><![CDATA[&lt;p&gt;The summary in 2nd paragraph is confusing, and makes it sounds as if this is something like a SAN technology - as far as I can tell from the links, this is simply a way for multiple PCI Express cards in a single system to be allocated to separate virtual machines.  The I/O virtualization part presumably makes it easy to connect a VM to different I/O resources, although SANs already do that so it&#039;s hard to see the value of this.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>The summary in 2nd paragraph is confusing, and makes it sounds as if this is something like a SAN technology &#8211; as far as I can tell from the links, this is simply a way for multiple PCI Express cards in a single system to be allocated to separate virtual machines.  The I/O virtualization part presumably makes it easy to connect a VM to different I/O resources, although SANs already do that so it&#8217;s hard to see the value of this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GaryO</title>
		<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/#comment-194914</link>
		<dc:creator><![CDATA[GaryO]]></dc:creator>
		<pubDate>Fri, 29 Feb 2008 06:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11654#comment-194914</guid>
		<description><![CDATA[&lt;p&gt;Great to see GigaOm covering more data center infrastructure!&lt;/p&gt;

&lt;p&gt;In addition to the folks mentioned delivering sophisticated path management, there are also companies trying to minimize the impact of application I/O requests by applying memory at the server, network, and storage layers, and delivering a &quot;virtual I/O&quot; response.&lt;/p&gt;

&lt;p&gt;But more importantly, how the heck did we go from:
1. We have Ethernet to
2. We have Ethernet and Fibre Channel to
3. We have Ethernet, Fibre Channel and InifiniBand to
4. We can put everything back on 10Gig Ethernet.&lt;/p&gt;

&lt;p&gt;Is it just me, or does this seem like we could have saved a few billion dollars over the last few years and skipped a couple of steps?&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Great to see GigaOm covering more data center infrastructure!</p>
<p>In addition to the folks mentioned delivering sophisticated path management, there are also companies trying to minimize the impact of application I/O requests by applying memory at the server, network, and storage layers, and delivering a &#8220;virtual I/O&#8221; response.</p>
<p>But more importantly, how the heck did we go from:<br />
1. We have Ethernet to<br />
2. We have Ethernet and Fibre Channel to<br />
3. We have Ethernet, Fibre Channel and InifiniBand to<br />
4. We can put everything back on 10Gig Ethernet.</p>
<p>Is it just me, or does this seem like we could have saved a few billion dollars over the last few years and skipped a couple of steps?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

