<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ext4 on Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/tags/ext4/</link>
    <description>Recent content in Ext4 on Experiment, Fail, Learn, Repeat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 Hairizuan Noorazman</copyright>
    <lastBuildDate>Mon, 31 Aug 2026 11:12:29 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/tags/ext4/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Persistent ext4 Roots for Multikernel Linux on Google Compute Engine</title>
      <link>https://www.hairizuan.com/persistent-ext4-roots-for-multikernel-linux-on-google-compute-engine/</link>
      <pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/persistent-ext4-roots-for-multikernel-linux-on-google-compute-engine/</guid>
      <description>&lt;p&gt;My first Multikernel Linux experiment on Google Compute Engine (GCE) showed that one VM could run a primary kernel and multiple child kernels at the same time. The children could use different kernel binaries, but their root filesystems were either minimal initramfs images or DAXFS. That left an important question unanswered: could a child kernel have a persistent, read-write ext4 root filesystem?&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
