Architecture

Documentation
Architecture
Clickable Diagram https://Home.D5E.dev
QEMU Guest Agent

Running the QEMU Guest Agent inside your Debian 13 VM on Proxmox 9 is strongly recommended
Install it inside the VM:
systemctl enable --now qemu-guest-agent``
Then, enable it in the VM’s settings in the Proxmox web UI (Options → QEMU Guest Agent → Yes).
This allows Proxmox to:

Gracefully shut down or reboot the VM.
Display IP addresses.
Freeze filesystems for snapshots.
Improve backup consistency.


  
      
          Environment
          Needs QEMU Guest Agent
          Why
      
  
  
      
          Proxmox Host
          No
          It’s the hypervisor itself
      
      
          VM (KVM)
          Yes
          Enables clean shutdown, IP reporting, backups
      
      
          LXC Container
          No
          Uses Proxmox’s native container controls
      
  

Proxmox control LXC Containers natively with pct enter, pct exec
, etc.
When installed in a VM, it lets Proxmox talk to the guest OS directly. That enables:
•	Safe shutdowns & reboots from the Proxmox UI (qm shutdown works cleanly instead of forcing ACPI power-off).
•	Freeze/thaw for live backups (Proxmox can quiesce the filesystem so backups are consistent).
•	Accurate IP reporting (Proxmox dashboard shows the VM’s internal IP addresses).
•	Better integration (time sync, guest status, etc.).
It doesn’t add much overhead and is considered best practice for production or homelab VMs.


sudo apt update
sudo apt install qemu-guest-agent -y
sudo systemctl enable qemu-guest-agent
sudo systemctl start qemu-guest-agent
systemctl status qemu-guest-agent</code></pre></div><div class="hextra-code-copy-btn-container hx:opacity-0 hx:transition hx:group-hover/code:opacity-100 hx:flex hx:gap-1 hx:absolute hx:m-[11px] hx:right-0 hx:top-0">
  <button
    class="hextra-code-copy-btn hx:group/copybtn hx:cursor-pointer hx:transition-all hx:active:opacity-50 hx:bg-primary-700/5 hx:border hx:border-black/5 hx:text-gray-600 hx:hover:text-gray-900 hx:rounded-md hx:p-1.5 hx:dark:bg-primary-300/10 hx:dark:border-white/10 hx:dark:text-gray-400 hx:dark:hover:text-gray-50"
    title="Copy code"
  >
    <div class="hextra-copy-icon hx:group-[.copied]/copybtn:hidden hx:pointer-events-none hx:h-4 hx:w-4"></div>
<div class="hextra-success-icon hx:hidden hx:group-[.copied]/copybtn:block hx:pointer-events-none hx:h-4 hx:w-4"></div>
  </button>
</div>
</div>
<p>On the Proxmox side, go to your VM’s Options → QEMU Guest Agent and set it to Enabled.</p>

  



QEMU Guest Agent
    

  Running the QEMU Guest Agent inside your Debian 13 VM on Proxmox 9 is strongly recommended

Install it inside the VM:

systemctl enable --now qemu-guest-agent``
Then, enable it in the VM’s settings in the Proxmox web UI (Options → QEMU Guest Agent → Yes).
This allows Proxmox to:

Gracefully shut down or reboot the VM.
Display IP addresses.
Freeze filesystems for snapshots.
Improve backup consistency.


  
      
          Environment
          Needs QEMU Guest Agent
          Why
      
  
  
      
          Proxmox Host
          No
          It’s the hypervisor itself
      
      
          VM (KVM)
          Yes
          Enables clean shutdown, IP reporting, backups
      
      
          LXC Container
          No
          Uses Proxmox’s native container controls
      
  

Proxmox control LXC Containers natively with pct enter, pct exec
, etc.
When installed in a VM, it lets Proxmox talk to the guest OS directly. That enables:
•	Safe shutdowns & reboots from the Proxmox UI (qm shutdown works cleanly instead of forcing ACPI power-off).
•	Freeze/thaw for live backups (Proxmox can quiesce the filesystem so backups are consistent).
•	Accurate IP reporting (Proxmox dashboard shows the VM’s internal IP addresses).
•	Better integration (time sync, guest status, etc.).
It doesn’t add much overhead and is considered best practice for production or homelab VMs.


sudo apt update
sudo apt install qemu-guest-agent -y
sudo systemctl enable qemu-guest-agent
sudo systemctl start qemu-guest-agent
systemctl status qemu-guest-agent</code></pre></div><div class="hextra-code-copy-btn-container hx:opacity-0 hx:transition hx:group-hover/code:opacity-100 hx:flex hx:gap-1 hx:absolute hx:m-[11px] hx:right-0 hx:top-0">
  <button
    class="hextra-code-copy-btn hx:group/copybtn hx:cursor-pointer hx:transition-all hx:active:opacity-50 hx:bg-primary-700/5 hx:border hx:border-black/5 hx:text-gray-600 hx:hover:text-gray-900 hx:rounded-md hx:p-1.5 hx:dark:bg-primary-300/10 hx:dark:border-white/10 hx:dark:text-gray-400 hx:dark:hover:text-gray-50"
    title="Copy code"
  >
    <div class="hextra-copy-icon hx:group-[.copied]/copybtn:hidden hx:pointer-events-none hx:h-4 hx:w-4"></div>
<div class="hextra-success-icon hx:hidden hx:group-[.copied]/copybtn:block hx:pointer-events-none hx:h-4 hx:w-4"></div>
  </button>
</div>
</div>
<p>On the Proxmox side, go to your VM’s Options → QEMU Guest Agent and set it to Enabled.</p>

  



HP 260 G2 Desktop Mini PC / Debian 12.8
Intel CPU i5-6200U 2.30ghz
RAM 8192 MB DDR4 / 2133 MHZ / Dual Channel <- Max ram: 32 GB
Adata SU630 SSD 240GB
Firmware: 04/26/2017
HDMI + DVI connector
https://support.hp.com/id-en/drivers/hp-260-g2-desktop-mini-pc/10049306

  Assets
    A custom tag
  
  Desktop
    A custom tag
  
  No Icon


VLans
    

Family
Guest
IoT
Iot/blackhole for stuff that is not supposed to reach internet
Server?
BHD
Trusted devices


management vlan (router, switches, proxmox cluster)




server vlan (kubernetes cluster, NAS, freeipa, ssh bastion)


camera vlan (no internet access) * CCTV (not in use)



gam - gaming consoles, xbox, playstations, media devices, tv, (no blocking, upnp enabled)

IPMI/MGMNT .x.x.13.0

https://en.wikipedia.org/wiki/Reserved_IP_addresses
https://www.reddit.com/r/networking/comments/5d4wv8/beyond_rfc1918_additional_ranges_for_private_use/
Environment	Needs QEMU Guest Agent	Why
Proxmox Host	No	It’s the hypervisor itself
VM (KVM)	Yes	Enables clean shutdown, IP reporting, backups
LXC Container	No	Uses Proxmox’s native container controls