Proxmox 9 Deployment: The Erasing and Rebirth of N100

📖 Meet the Cyber Foundation: Proxmox VE (PVE)

Before we commit “homicide” on the hardware, let’s meet our protagonist.

Proxmox Virtual Environment is an open-source server virtualization management solution based on QEMU/KVM and LXC. You can easily manage virtual machines, containers, high-availability clusters, storage, and networks through an extremely easy-to-use Web interface or CLI. The project is open-source under the GNU AGPLv3 license and is developed and maintained by Proxmox Server Solutions GmbH. —— Excerpt from official documentation

In our Homelab circle, we affectionately call it PVE.

Compared to VMware ESXi, which is extremely picky about hardware and charges at every turn, PVE is a “Cyber Bodhisattva.” It’s not only completely free and open-source, but also extremely tolerant of hardware—whether it’s an enterprise Dell workstation or our 12GB RAM AOC MOSS N100, it will take root stably and squeeze out every drop of hardware performance.

Foreman’s Blast Warning: All in One vs. All in Boom

The most tempting yet hardcore way to play with PVE is called “All in One” (AIO): using its virtualization power to run a soft router (like OPNsense), NAS storage (like TrueNAS), media server, and various Linux test nodes all on one physical machine.

But this is both heaven and hell. The Foreman must give you a heads-up: The end of All in One is often All in Boom.

Once the PVE host layer crashes, or if you make a mistake while configuring network passthrough (like losing NIC connectivity), your home Wi-Fi will instantly paralyze, and the data in your NAS will temporarily disconnect. What follows will be the ruthless “Gank” from your family (network outage warnings) and your desperate silhouette reinstalling in the dead of night.

⚠️ Disclaimer: This construction blueprint is for reference only. No two network topologies or hardware environments are identical in the world. Please adjust flexibly based on your own actual situation (especially IP addresses and physical NIC names). If you blindly copy parameters and cause a home network crisis, this Foreman is not responsible! Tinkering involves risks; construction requires caution.

---

You can install Proxmox VE (PVE) directly on physical hardware using a standard ISO image. This is the absolute foundation for building a cyber studio.

Foreman’s Broadcast

While there are countless PVE installation tutorials online, what’s recorded here is the “Foundation Pouring” process exclusive to this lab. If you just want to see a smooth installation demo, watch the video below; if you want to see how I “stepped into the pits,” read on.

---

🧱 Pre-construction Requirements

Before ruthless execution on the N100, ensure you have the following “crime tools” at hand:

• The Victim: An AOC MOSS N100 with 12GB RAM (or your own machine).
• The Tool: A USB drive of at least 8GB.
• Command Center: A Mac or Win machine (for downloading images and flashing the boot drive).
• Network Conditions: An ethernet cable plugged into the N100, ensuring the network assigned by the main router is functional.
• VPN/Proxy Environment: To avoid various strange network issues.
• Version Note: This tutorial applies to proxmox-ve_9.1-1.

---

📜 Official Blueprints

When encountering metaphysical problems, checking the official manual is always the safest choice:

• 🌐 Proxmox Official Website
• 📥 ISO Image Downloads
• 📖 Official Wiki Documentation
• 💬 Community Forum

---

🎬 Construction Walk-through Video

If you fear BIOS booting and black-and-white installation interfaces, click this video to build some psychological resilience.

---

🔨 Core Installation Steps

1. Acquire the “Blueprint” (Download Image)

   Go to the PVE official website to download the latest ISO image. This file, less than 2GB, is the absolute foundation that will support our entire cyber studio.

   • 🌐 Proxmox Official Site
   • 📥 Direct ISO Download

2. Forge the “Takeover” USB (Flash Image)

   Prepare your 8GB USB drive. On a Mac or Windows machine, use a flashing tool to inject the ISO soul into the USB drive.

   • 🍎 For Mac Users: BalenaEtcher (Great UI, brainless 3-step flashing)
   • 🪟 For Win Users: Rufus (The classic, lightweight, and hardcore tool)

   Rufus Flashing Warning

   If you choose Rufus, when it asks for the writing mode, you MUST, DEFINITELY, ABSOLUTELY select “Write in DD Image mode”! If you select the default ISO mode, you’ll likely be staring at a screen full of errors when booting on the N100.

   

3. BIOS Takeover and Low-level Tuning (Critical)

   Plug the flashed USB into the N100, power it on, and the moment the screen lights up, frantically tap Del (or F2 on some machines) to force your way into the physical brain (BIOS).

   Foreman’s Disclaimer: Local Adaptation

   Every motherboard manufacturer has their own “unique aesthetic” for BIOS menu layouts. The parameters mentioned below may have slight name variations (e.g., VT-d might be called IOMMU). This tutorial uses our lab’s AOC MOSS as an example; please adapt based on your actual hardware!

   To let PVE completely take over the hardware, find and modify these four core parameters:

   • 🔓 Disarm Defense (Secure Boot) In the Security tab, find Secure Boot and set it ruthlessly to Disabled. This Microsoft lock is the culprit preventing Linux from taking over; it must be smashed.
   • 🧬 Unlock Genes (VT-x / VT-d) In Advanced or CPU Configuration, find Intel Virtualization Technology and VT-d. Set both to Enabled. This is the physical basis for running VMs.
   • ⚡ Auto-Power On (AC Recovery) In Power or Chipset, find Restore AC Power Loss or State After G3 and set it to Power On. As a qualified cyber studio, it must start working the moment power is restored.
   • 🚀 Forced Usurpation (Boot Order) In the Boot tab, set Boot Option #1 to your USB drive (usually labeled UEFI: Your USB Brand).

   After saving with F10, you’ll be greeted by PVE’s sexy black installation interface instead of the Windows logo.

4. Basic Identity Entry (System & Auth)

   After the code scrolls, enter the PVE Graphical Installer. Agree to the terms and fill in the following:

   • Target Harddisk: Select the built-in 256GB SSD. (Foreman’s advice: Don’t touch ZFS with 12GB RAM; stick to ext4 or xfs).
   • Country/Timezone: Enter China, timezone locks to Asia/Shanghai.
   • Password: Set your root super password. Write it down immediately! Resetting a forgotten PVE password is anti-human.
   • Email: Enter your actual email for notifications.
   

5. Network Addressing Configuration

   This is the step most likely to cause “disconnection.” Remember: The tutorial is static, but your environment is alive.

   • Management Interface: The N100 has two ports. Foreman’s Strong Suggestion: Only plug in one ethernet cable connected to the main router during installation! The active port will show as Green (Active) in the dropdown. Choose the green one (usually enp1s0 or eth0).

   Construction Taboo: No Blind Copying

   The parameters below are based on my Static IP Asset Table. If your main router segment isn’t 192.168.100.x, you MUST modify them accordingly!

   Parameters for reference:

   # Cyber Foundation Network Config (Adjust to your segment!)
   Hostname: pve-studio.homelab.local
   IP Address: 192.168.100.50/24      # 👈 This is MY IP! Use your own!
   Gateway: 192.168.100.1             # Points to your main router
   DNS Server: 192.168.100.1          # Usually matches the gateway

   

6. Unplug and Takeover (Reboot & Takeover)

   After confirming, click Install.

   • Once Installation successful appears, click Reboot.
   • The moment the screen goes black, pull out the USB drive!
   • Windows 11 is now dead; PVE officially takes over the N100. The screen will stop at a black-and-white login prompt with a URL.

---

🚪 Post-Installation Access

Go back to your Mac Mini, open a browser, and enter:

https://192.168.100.50:8006 (Use the IP you actually set!)

Key to Success

1. It MUST be https, otherwise you’ll get a white screen.
2. The browser will warn about “Not Private”; click “Advanced” -> “Proceed”.
3. Log in with root and your installation password.

---

🛠️ Advanced Construction: Day 1 Optimization

After logging in, the first task isn’t creating VMs, but “finishing” the system. Select the pve-studio node on the left and click >_ Shell on the top right.

Important Notice for Mirroring

The following repository optimizations are specifically intended for users in Mainland China to speed up updates. If you are outside China, please skip these mirror changes and use the official Debian/Proxmox repositories.

0. Prepare Your Tools (SSH Connection)

The web-based Shell can be glitchy with copy-pasting. The Foreman suggests using a professional SSH tool from your command center to connect to root@192.168.100.50.

• 🍎 For Mac: Terminal, iTerm2, FinalShell, or Termius.
• 🪟 For Win: Windows Terminal, MobaXterm, or Xshell.

1. Remove the “No Valid Subscription” Popup

sed -i.bak '/.*data\.status.*active/{s/!//;s/active/NoMoreNagging/}' /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js && systemctl restart pveproxy.service

2. Backup Debian Sources

cp /etc/apt/sources.list.d/debian.sources /etc/apt/sources.list.d/debian.sources.bak

3. Replace with Tsinghua Mirror (Mainland China Only)

cat > /etc/apt/sources.list.d/debian.sources << 'EOF'
Types: deb
URIs: [https://mirrors.tuna.tsinghua.edu.cn/debian/](https://mirrors.tuna.tsinghua.edu.cn/debian/)
Suites: trixie trixie-updates trixie-backports
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: [https://security.debian.org/debian-security/](https://security.debian.org/debian-security/)
Suites: trixie-security
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
EOF

Disable Enterprise Repo

nano /etc/apt/sources.list.d/pve-enterprise.sources

Add No-Subscription Repo (Tsinghua Mirror)

cat > /etc/apt/sources.list.d/pve-no-subscription.sources << 'EOF'
Types: deb
URIs: [https://mirrors.tuna.tsinghua.edu.cn/proxmox/debian/pve](https://mirrors.tuna.tsinghua.edu.cn/proxmox/debian/pve)
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

4. System Update

apt update && apt dist-upgrade -y

5. Enable IOMMU Passthrough

sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT="quiet"/GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_port_pm=off"/' /etc/default/grub
update-grub

6. Reboot

reboot

---

7. Validation

Check if IOMMU is active after reboot:

dmesg | grep -e DMAR -e IOMMU

If you see IOMMU enabled, congratulations! Your N100 is in peak condition.

---

📂 Project Archiving

Record your core parameters in your knowledge base.

Foreman’s Blood and Tears Warning

Update this template with YOUR actual parameters!

## 🚀 PVE Core Asset Memo
- **Management IP**: 192.168.100.50      # 👈 Your actual IP
- **Gateway**: 192.168.100.1             # 👈 Your actual Gateway
- **Hardware**: AOC MOSS M3L (N100 / 12G RAM / 256G SSD)
- **Tuning**: IOMMU enabled, pcie_port_pm=off, Tsinghua mirror applied.

---

🔗 The Cyber Foreman’s Secret Bookmarks

How can you tinker with PVE without standing on the shoulders of giants? Here are a few wild artifacts and communities that will save you a few strands of hair. When the official documentation can’t solve your metaphysical problems, come here for answers.

• 🪄 Proxmox VE Helper-Scripts (One-Click Magic)
  • Foreman’s Note: An incredibly awesome community-driven script library. Browse, install, and manage containers (LXC) and VMs with a single command. This is the ultimate cheat code for our “day shift” construction, significantly reducing the pain of typing commands until your hands cramp.
• 🌍 Reddit r/Proxmox (Global Server Crash Symposium)
  • Foreman’s Note: The gathering place for PVE players worldwide. Whenever you encounter some outrageous metaphysical bug that you can’t find on Google, search here. There’s a high probability you’ll find that some veteran stepped into the exact same pit three years ago.

👷‍♂️ The Cyber Foreman’s Hotline

If you’ve scoured the godly sites above, and even AI starts hallucinating from your endless questions, yet your cyber-mystery remains unsolved… don’t panic. You can always hail me through the comms channels in the Cyber Wasteland Guide.

Even though this Foreman is essentially a “cyber-noob” who relies on metaphysical troubleshooting, and I probably can’t offer any enterprise-grade solutions. But hey… what if our machines blew up in the exact same pit? It never hurts to discuss the fancy ways our servers died and give it a try!

---

➡️ Next Steps

• Ultimate Dark Magic: N100 GPU SR-IOV Virtualization: Split one GPU into 7.
• Configure OPNsense: Set up the lab gatekeeper.
• Deploy First Blog Test Node: Start your acting career.