<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Virtualization Wtf on yomimono - something to read</title>
    <link>http://localhost:1313/tags/virtualization-wtf/</link>
    <description>Recent content in Virtualization Wtf on yomimono - something to read</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 07 Oct 2014 14:13:03 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/tags/virtualization-wtf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Virtualization: WTF</title>
      <link>http://localhost:1313/blog/2014/10/07/virtualization-wtf/</link>
      <pubDate>Tue, 07 Oct 2014 14:13:03 +0000</pubDate>
      <guid>http://localhost:1313/blog/2014/10/07/virtualization-wtf/</guid>
      <description>&lt;p&gt;For reasons that don&amp;rsquo;t need exploring at this juncture, I decided to start reading through &lt;a href=&#34;http://pages.cs.wisc.edu/~remzi/Classes/838/Spring2013/&#34;&gt;a bunch of papers on virtualization&lt;/a&gt;, and I thought I&amp;rsquo;d force myself to actually do it by publicly committing to blogging about them.&lt;/p&gt;&#xA;&lt;p&gt;First on deck is &lt;a href=&#34;http://web.stanford.edu/class/cs240/readings/disco.pdf&#34;&gt;Disco: Running Commodity Operating Systems on Scalable Multiprocessors&lt;/a&gt;, a paper from 1997 that itself &amp;ldquo;brings back an idea popular in the 1970s&amp;rdquo; &amp;ndash; run a small virtualization layer between hardware and multiple virtual machines (referred to in the paper as a virtual machine monitor; &amp;ldquo;hypervisor&amp;rdquo; in more modern parlance).  Disco was aimed at allowing software to take advantage of new hardware innovations without requiring huge changes in the operating system.  I can speculate on a few reasons this paper&amp;rsquo;s first in the list:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;if you have a systems background, most of it is intelligible with some brow-furrowing&lt;/li&gt;&#xA;&lt;li&gt;it goes into a useful level of detail on the actual work of intercepting, rewriting, and optimizing host operating systems&amp;rsquo; access to hardware resources&lt;/li&gt;&#xA;&lt;li&gt;the authors went on to found VMware, a massively successful virtualization company&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;I read the paper intending to summarize it for this blog, but I got completely distracted by the paper&amp;rsquo;s motivation, which I found both interesting and unexpected.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
