Chapters: 
Camelot

Why Use QEMU/KVM with Virtual Machine Manager? ⛩️

These tools are native to Linux (especially RHEL-based distros), open-source, and tightly integrated:

🔹 Benefits over VMware ESXi 

| Feature                              | QEMU/KVM + virt-manager     | VMware ESXi (no vCenter)                |
| ------------------------------------ | --------------------------- | --------------------------------------- |
| 🛠 Free & Open Source                | Yes                         | No (ESXi is free, but limited)          |
| 🧩 GUI Built-in (virt-manager)       | Yes, usable over SSH        | No native GUI without vCenter           |
| 🔐 SELinux + RHEL Hardening          | Native                      | Not applicable                          |
| 🧰 CLI + Automation (libvirt, virsh) | Excellent                   | VMware CLI is powerful, but proprietary |
| 📦 Easy to use as container host     | Yes (use Podman inside VMs) | Requires more setup                     |
| 🛡️ No phoning home                   | Yes                         | No comment 😉                           |

 

⛩️ Thought Shift: From "Just Containers" to "VMs That Host Containers"

You're framing it right:

  • Use KVM to provision VMs (RHEL/Rocky 8/9)

  • Use Podman inside those VMs to run container workloads

  • You gain:

    • Isolation between major systems

    • Snapshot/restore ability via libvirt

    • Resource control at VM level (RAM, CPU pinning, etc.)

    • Better air-gap practices (e.g. offline updates via ISO)

 

⛩️ Initial Setup - Camelot

  1. On Camelot, install virt-manager (CLI or GUI).

  2. Create a RHEL 8 or 9 VM with a GUI environment.

  3. Set virtio for disk/network for speed.

  4. Use bridge or macvtap for networking if it must talk on the LAN.

  5. Optionally install cockpit inside the VM to make admin easier.

 

⛩️ Bonus: Libvirt Snapshot + Automation

You can: 

virsh snapshot-create-as myvm snap1 "Pre-container-load snapshot"