<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VMware on YHY Study Website</title><link>https://ryan.0412.online/en/tags/vmware/</link><description>Recent content in VMware on YHY Study Website</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 30 Sep 2026 21:25:01 +0800</lastBuildDate><atom:link href="https://ryan.0412.online/en/tags/vmware/index.xml" rel="self" type="application/rss+xml"/><item><title>Installing a Custom Linux Kernel in a Virtual Machine</title><link>https://ryan.0412.online/en/blog/custom-linux-kernel-in-vm/</link><pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate><guid>https://ryan.0412.online/en/blog/custom-linux-kernel-in-vm/</guid><description>&lt;p&gt;This article has one goal: &lt;strong&gt;compile and install a custom kernel in Ubuntu running inside VMware, then load a .ko module I wrote myself&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Compilation and kernel replacement both happen in that virtual machine. They consume CPU, memory, and disk space and involve GRUB. Unstable networking can interrupt long builds or SSH sessions; without booting the new kernel, the module will not match the running version. The order is therefore static IP first, custom kernel second, and module last.&lt;/p&gt;</description></item></channel></rss>