<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Virtualization on Nitin Gupta</title>
    <link>https://nitingupta.dev/tags/virtualization/</link>
    <description>Recent content in Virtualization on Nitin Gupta</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>ngupta@nitingupta.dev (Nitin Gupta)</managingEditor>
    <webMaster>ngupta@nitingupta.dev (Nitin Gupta)</webMaster>
    <lastBuildDate>Sat, 19 Jun 2010 05:22:00 -0700</lastBuildDate>
    <atom:link href="https://nitingupta.dev/tags/virtualization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Faster compilation with distcc</title>
      <link>https://nitingupta.dev/post/faster-compilation-with-distcc/</link>
      <pubDate>Sat, 19 Jun 2010 05:22:00 -0700</pubDate><author>ngupta@nitingupta.dev (Nitin Gupta)</author>
      <guid>https://nitingupta.dev/post/faster-compilation-with-distcc/</guid>
      <description>&lt;p&gt;Often, you have more than one system at your disposal but no clear way&#xA;of distributing your compilation workloads over to all or some of them.&#xA;They might be running different OSes which makes it look even more&#xA;difficult. In my case, I have one laptop (2 cores) and a desktop (4&#xA;cores) connected with a WiFi network. The laptop runs Linux (Fedora 13&#xA;64-bit) while the desktop runs Windows 7 (64-bit). I wanted to somehow&#xA;offload Linux kernel compilation over to my powerful desktop and keep my&#xA;laptop cool :)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Compressed RAM disk for Windows, The Virtual Way!</title>
      <link>https://nitingupta.dev/post/compressed-ram-disk-for-windows-the-virtual-way/</link>
      <pubDate>Sun, 30 May 2010 06:53:00 -0700</pubDate><author>ngupta@nitingupta.dev (Nitin Gupta)</author>
      <guid>https://nitingupta.dev/post/compressed-ram-disk-for-windows-the-virtual-way/</guid>
      <description>&lt;p&gt;Recently, I developed Linux kernel driver which creates generic RAM&#xA;based compressed block devices (called &lt;strong&gt;zram&lt;/strong&gt;). Being RAM disks, they&#xA;do not provide persistent storage but there are many use cases where&#xA;persistence is not required: /tmp, various caches under /var, swap disks&#xA;etc. These cases can benefit greatly from high speed RAM disks along&#xA;with savings which compression brings!&lt;/p&gt;&#xA;&lt;p&gt;However, all this seems to be completely Linux centric. But with&#xA;virtualization, zram can be used for Windows too! The trick is a expose&#xA;zram as a ‘raw disk’ to Windows running inside a Virtual Machine (VM). I&#xA;will be using VirtualBox as example but exposing raw disks should be&#xA;supported by other Virtualization solutions like VMware, KVM too.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
