Avi Kivity's Kernel Developer Blog
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. Unfortunately the VMware kernel is proprietary, so that means
VMware has to write and maintain the entire I/O stack. That means a slow
development rate, and that your hardware may take a while to be supported.
Xen took the maintainability route, by doing all I/O within a Linux guest,
called "domain 0". By reusing Linux for I/O, the Xen maintainers don't have
to write an entire I/O stack. Unfortunately, this eats awa... (more)