PVE: Cyber Studio & Accident Simulator

“Don’t ask me if this architecture is stable; if it were too stable, how would I update my blog?”

Welcome to the “Full-Scene Accident Simulation and Drill Center” of the Cyber Construction Site.

Let’s be clear: this N100 host does not carry any core family productivity (family internet relies on the main router; my productivity relies on the Mac Mini). Every VM, VLAN partition, and cluster orchestration here is purely a 1:1 simulation range built for writing blogs, reproducing bugs, and capturing error logs.

Here, memory overcommitment is standard operating procedure, and system crashes are simply part of the script.

---

🎬 Actors on Set: VM & LXC List

This 12GB of physical memory is crammed with cyber actors ready to perform “how to step into a pit correctly” at any moment. Their existence depends entirely on what I feel like writing about today.

root@pve-studio:~# qm list && pct list —sort=vmid

ID / Type	Quota (vCPU/RAM)	Script (Node & Link)	Addressing (IP/VLAN)	Status & Foreman’s Rants
100 🖥️ VM	2 Core 2GB RAM	🛡️ Virtual Gateway OPNsense	192.168.100.247 vBridge	🟢 Ready to Lock Out The resident antagonist. Used to demonstrate firewall rules and how to vividly lock myself out of the gateway.
101 🖥️ VM	2 Core 4GB RAM	💾 TrueNAS Storage	10.10.20.x VLAN 20	🛑 Static Prop Dedicated to ZFS array demos. Shut down after screenshots; 4GB of RAM for TrueNAS is a total “extra” role.
102 🖥️ VM	2 Core 2GB RAM	☸️ K3s Master	10.20.10.10 VLAN 10	🟡 Sick Rehearsal Core material for the “Cannon Swatting Mosquitoes” series. Shows how an enterprise K8s control plane survives on 2GB RAM.
103 🖥️ VM	4 Core 4GB RAM	☸️ K3s Node 01	10.20.10.11 VLAN 10	🚷 Cooperative Acting Responsible for heavy Docker loads. Frequently plays out “node hang” and “Pod migration” thriller scenes.
104 🖥️ VM	2 Core 2GB RAM	🐳 Ops Infrastructure	10.20.30.10 VLAN 30	🟢 Stage Manager Runs NPM reverse proxy and Docker. The off-site rescue team for when K3s blows up, ensuring blog assets remain accessible.
105 📦 LXC	1 Core 512MB RAM	📊 Monitoring Command Deck	10.20.30.5 VLAN 30	🚧 Taking Scores A humble 512MB LXC. Runs Grafana dashboards to visualize the data of the N100 smoking under full load.
106 🖥️ VM	4 Core 6GB RAM	🪟 Win11 Desktop (VDI)	10.20.50.x VLAN 50	💤 Post-production Dust Stress test prop. Permanently sealed after a single “boot at full load” screenshot to prevent the N100 from actually catching fire.
107 🖥️ VM	2 Core 2GB RAM	🐧 Linux Desktop (VDI)	10.20.50.y VLAN 50	💤 Post-production Dust Same as above. Proves I can host Linux cloud desktops. Screenshot done, actor dismissed.

💡 Blog-Driven Architecture (BDA)

The physical memory of this N100 is only 12GB, yet the combined quota of the machines above reaches 22.5GB.

Surviving such insane overcommitment depends entirely on my precise “Production Schedule”: when writing router tutorials, the K3s nodes are powered off; when deploying Kubernetes, TrueNAS and Windows stay dead in their graves.

This PVE host is like a dedicated cyber studio. As long as I don’t get greedy and try to pull up all the machines at once, it will continuously provide the most authentic, hard-core, and “bloody” accident troubleshooting logs for my blog.