Skip to content

Instantly share code, notes, and snippets.

@Impact123

Impact123/Why Virtualize.md

Last active March 1, 2025 05:13
Show Gist options
  • Save Impact123/c23c36eafe1672ec056233e450a86ae2 to your computer and use it in GitHub Desktop.
Save Impact123/c23c36eafe1672ec056233e450a86ae2 to your computer and use it in GitHub Desktop.
Download ZIP
Why Virtualize
Raw
Why Virtualize.md

Why Virtualize

you get full backups, snapshots, a build in monitor to debug. You can also better utilize the hardware. Not every service (very few imho) are feasible to run inside HAOS

easy troubleshooting (basically a build in monitor and keyboard), snapshots to test and then potentially revert things you otherwise would be too afraid to try. The ability to backup a whole machine and run other VMs/Containers and so on

I recommend running critical/unrelated things (adguard, unifi or bitwarden for example) or those that require flexibility outside of HAOS if you can as these will go down on OS updates. You can't do that with a bare metal HAOS install.

Some of my previous answers to why run HAOS virtualized. Just some of the benefits and reasons why I recommend it.
Also see posts like these which one can find with queries like virtualization benefits: https://old.reddit.com/r/homelab/comments/qw4bqn/why_use_virtual_machines/

I recommend Proxmox VE. Here's a quick start guide for HA: https://www.derekseaman.com/2023/10/home-assistant-proxmox-ve-8-0-quick-start-guide-2.html
And here a tips list: https://gist.github.com/Impact123/3dbd7e0ddaf47c5539708a9cbcaab9e3
Even if one only runs HAOS I would recommend it due to the benefits.

Here's why I wouldn't run HAOS bare-metal without those benefits:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment