<?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 Tony Metzidis</title>
    <link>https://tonym.us/tag/virtualization.html</link>
    <description>Recent content in Virtualization on Tony Metzidis</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 06 Oct 2026 16:20:00 -0700</lastBuildDate>
    <atom:link href="https://tonym.us/tag/virtualization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Security Tax in WSL3: Benchmarking Kernel Mitigations Against WSL 2.x</title>
      <link>https://tonym.us/wsl3-kernel-mitigations-tax-benchmark.html</link>
      <pubDate>Tue, 06 Oct 2026 16:20:00 -0700</pubDate>
      <guid>https://tonym.us/wsl3-kernel-mitigations-tax-benchmark.html</guid>
      <description>&lt;p&gt;In our earlier look at &lt;a href=&#34;https://tonym.us/wsl2-security-tax-reclaiming-performance.html&#34;&gt;The Security Tax in WSL 2&lt;/a&gt;, we showed how kernel-level mitigations for CPU speculative execution vulnerabilities (Spectre, Meltdown, Retbleed) imposed a steep penalty on developer tasks. On a real-world Go backend compilation workload, turning off mitigations slashed kernel system time by &lt;strong&gt;45.7%&lt;/strong&gt; and delivered a &lt;strong&gt;31.7% drop in wall-clock compile time&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;With the rollout of &lt;strong&gt;WSL v3.0.2&lt;/strong&gt; (running Linux kernel &lt;code&gt;6.18.40.1-microsoft-standard-WSL2&lt;/code&gt;), how does the security tax hold up today? Does modern hypervisor paravirtualization eliminate the overhead, or are developers still paying an invisible performance toll on syscall-heavy workloads?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
