Proxmox is convenient, I run it at home. However it feels hacky: it's a bunch of scripts put together on top of Debian (with ZFS pre-installed) and I'm not betting the house on it.
I try to rely on Proxmox as little as possible and only care about the VMs. Ideally I should be able to, seamlessly, replace Proxmox with FreeBSD and bhyve (that's the plan at least).
So Tesco used to run VMs on VMWare and now moved the VMs to Proxmox: it's kinda the point of VMs. They should be easy to run somewhere else. If you've got any kind of "vendor lock-in" to your hypervisor, you're doing it wrong.
Re Proxmox: it's basically Perl scripts plus a UI for noobs (like me) in JavaScript. It's all "click click click / drop-down menu / click".
What could possibly go wrong here?
It simply doesn't feel like a serious enough project.
But in any case I don't care much: automated provisioning of my VMs is what I care about, no matter the hypervisor.
Proxmox is convenient, I run it at home. However it feels hacky: it's a bunch of scripts put together on top of Debian (with ZFS pre-installed) and I'm not betting the house on it.
I try to rely on Proxmox as little as possible and only care about the VMs. Ideally I should be able to, seamlessly, replace Proxmox with FreeBSD and bhyve (that's the plan at least).
So Tesco used to run VMs on VMWare and now moved the VMs to Proxmox: it's kinda the point of VMs. They should be easy to run somewhere else. If you've got any kind of "vendor lock-in" to your hypervisor, you're doing it wrong.
Re Proxmox: it's basically Perl scripts plus a UI for noobs (like me) in JavaScript. It's all "click click click / drop-down menu / click".
What could possibly go wrong here?
It simply doesn't feel like a serious enough project.
But in any case I don't care much: automated provisioning of my VMs is what I care about, no matter the hypervisor.