<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://avikivity.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Avi Kivity</title>
 <link>http://avikivity.sys-con.com/</link>
 <description>Latest News from Avi Kivity</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Mon, 30 Nov 2009 01:58:46 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>I/O Virtualization: Maintainability vs Performance</title>
 <link>http://avikivity.sys-con.com/node/558153</link>
 <description>I/O performance is of great importance to a hypervisor. I/O is also a huge maintenance burden, due to the large number of hardware devices that need to be supported, numerous I/O protocols, high availability options, and management for it all. VMware opted for the performance option, but putting the I/O stack in the hypervisor. Xen took the maintainability route.&lt;p&gt;&lt;a href=&quot;http://avikivity.sys-con.com/node/558153&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 05 May 2008 18:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://avikivity.sys-con.com/node/558153</guid>
 <comments>http://avikivity.sys-con.com/node/558153#feedback</comments>
</item>
</channel>
</rss>
