> The third is the most important, and it is the thread of this blog: open source is text. A Proxmox config is files. So it is versionable in Git, readable by an AI, auditable, reproducible. A proprietary hypervisor is a black box that neither Git nor my AI agent can really work with. Moving to Proxmox was not just a change of software: it made my infrastructure legible to my tools.
I agree with that point and AI is gonna help drive an important change there that was long overdue. I remember once at the beginning of my career working with a bunch of consultants that all could not even write simple Python and as a result of that every SOP was basically a bunch of GUI operations, mostly over RDP, so impossible to script. I hope this kind of stuff is now going away with AI, since even the non-coders can code now and will finally understand why GUIs suck. Thank LLMs for that.
Awesome work! Overall this is a big win for IT at this org.
>The real gain is that my virtualization layer became text: versioned in Git, watched by an open-source stack I built alongside it, backed up with immutable snapshots that are my first line of defense against ransomware, and above all legible to my tools, including my AI agent.
All of that can be done on Windows Server today with PowerShell tho.
IMHO, the real benefits of Proxmox over Hyper-V are:
1. Access to special hardware features via the Linux kernel, like GVT-g and SR-IOV for graphics acceleration.
2. Much better support for network configuration, monitoring, and packet capture.
2. ZFS
But there are some real reasons to continue with Hyper-V too, like:
1. Better support for Sleep / Wake-on-LAN if you wanted to save power with unused hypervisor capacity.
2. Running and developing for Windows containers.
3. The org has a VDI or remote desktop gateway that leverages Hyper-V's VMConnect protocol.
> The third is the most important, and it is the thread of this blog: open source is text. A Proxmox config is files. So it is versionable in Git, readable by an AI, auditable, reproducible. A proprietary hypervisor is a black box that neither Git nor my AI agent can really work with. Moving to Proxmox was not just a change of software: it made my infrastructure legible to my tools.
I agree with that point and AI is gonna help drive an important change there that was long overdue. I remember once at the beginning of my career working with a bunch of consultants that all could not even write simple Python and as a result of that every SOP was basically a bunch of GUI operations, mostly over RDP, so impossible to script. I hope this kind of stuff is now going away with AI, since even the non-coders can code now and will finally understand why GUIs suck. Thank LLMs for that.
Man did I hate those screenshot driven SOPs!
Awesome work! Overall this is a big win for IT at this org.
>The real gain is that my virtualization layer became text: versioned in Git, watched by an open-source stack I built alongside it, backed up with immutable snapshots that are my first line of defense against ransomware, and above all legible to my tools, including my AI agent.
All of that can be done on Windows Server today with PowerShell tho.
IMHO, the real benefits of Proxmox over Hyper-V are:
1. Access to special hardware features via the Linux kernel, like GVT-g and SR-IOV for graphics acceleration.
2. Much better support for network configuration, monitoring, and packet capture.
2. ZFS
But there are some real reasons to continue with Hyper-V too, like:
1. Better support for Sleep / Wake-on-LAN if you wanted to save power with unused hypervisor capacity.
2. Running and developing for Windows containers.
3. The org has a VDI or remote desktop gateway that leverages Hyper-V's VMConnect protocol.
[flagged]