It’s good to see what this article details into it and how some can pull all this together … for free (or for a small sum).
It’s good to see what this article details into it and how some can pull all this together … for free (or for a small sum).
I don't recall this being an issue before.
I ended up re-installing TrueNAS Scale beta, which I had installed and tried, but ran into a problem. Ended up finding the solution on the forums, something related to bridged or VLAN interfaces not coming up.
In the end I probably will just install Ubuntu and put Ganeti on these boxes, since that's been really reliable for me at work. I was actually hoping to try out Proxmox to possibly move to at work.
Has a pfSense/FreeBSD VM for a gateway and a bunch of VMs on a detached bridge. Also have several more bridges for test VMs for real-world airgapped network setup.
8 different OS distros. Also am tweaking a MIPS and a M1 QEMUs outside of Proxmox .
runs very quiet.
so now it’s my home datacenter.
One thing I had to do recently though is swap pfsense for Untangle because of drastically better FQ-CoDel implementation in Untangle.
Not sure why would one even do that.
:-(However, the YouTube breakdown by Battle(non)sense was conclusive (and is confirmed in my case in undeniable ways) so I switched.
Thing is it's hard to re-allocate this partition, and that's where all the iso images, and the backups go.
I tried to migrate a vm and boom - it filled up.
I tried to figure out how to reallocate it, but in the end, I found this (sort of hacky) solution documented:
https://pve.proxmox.com/wiki/Logical_Volume_Manager_(LVM)
basically:
# lvcreate -n vz -V 200G pve/data
# mkfs.ext4 /dev/pve/vz
# echo '/dev/pve/vz /var/lib/vz ext4 defaults 0 2' >> /etc/fstab
you migrate the stuff from /var/lib/vz to the new location and you have 200G for iso images/etcWhy this has to fight for storage from the root system, or why it's not easily expandable is a head-scratcher. I think it might be better to have a dedicated boot debian partition, a resizable/easily growable pve partition, then storage that can be allocated to vms/containers.
but yeah - that stopped me in my tracks, and when I'm doing it on a home machine you just don't have the time to chase this stuff down.
Made more sense to have a second drive or second but largest LVM to play with and store all things VM.
So confident that I disabled the Proxmox 'local' drive.
If you want full control of the disk layout and maybe want to do some more custom stuff, consider installing a base Debian and then install Proxmox VE on top of it [1].
The PVE installer makes it easy to get a system up and running quickly but is opinionated what the disk layout should be. That of course might not be working for everyone.
[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#advanc... [1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_insta...