<?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 Aadarsha Khadka</title><link>https://aadarshakhadka.com.np/practice-log/virtualization/</link><description>Recent content in Virtualization on Aadarsha Khadka</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 22 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aadarshakhadka.com.np/practice-log/virtualization/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux Virtualization Internals: From Intel VT-x to KVM, QEMU, and libvirt</title><link>https://aadarshakhadka.com.np/practice-log/virtualization/001-introduction/</link><pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate><guid>https://aadarshakhadka.com.np/practice-log/virtualization/001-introduction/</guid><description>&lt;h3 id="virtualization"&gt;Virtualization&lt;/h3&gt;
&lt;p&gt;Virtualization is the abstraction of physical computing resources to create isolated virtual resources that can be independently managed and used.
In the context of server virtualization, a physical machine&amp;rsquo;s CPU, memory, storage, and I/O resources are abstracted and presented to one or more &lt;strong&gt;virtual machines (VMs)&lt;/strong&gt;.
Each VM is provided with virtual hardware and can run its own operating system.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;A VM is not physical hardware. It is an isolated execution environment whose hardware interface is virtualized.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>