KVM (RHV, OLVM, PVE, SCHC) • Re: Why is the Proxmox Worker Proxy So Different?

Yes I understand. My question is why was this approach taken? It has so many limitations but no apparent advantages. I'm struggling to think of a technical justification or requirement.

Pros:

* ... I suppose it's mostly automatic?

Cons:

* Cannot transfer years of knowledge from the managed server + agent approach.
* Cannot use organization templates and SOPs for hardened and optimized systems. E.g.
* Unable to install IDS/IPS solution on appliance.
* Unable to apply tunables like TCP buffer or congestion control algorithm, very important for good bandwidth over high latency high throughput connections.
* Unable to manage log forwarding to SIEM.
* Honestly could go on a while here so let's cut it there.
* Restricted capabilities due to needing to redo years of lessons learned from prior approach, e.g. the "Run server on this side" option.

An appliance option I'm sure is favored and works great for some users, but it shouldn't replace the agent on a managed server approach using the tried and true Veeam services. I would ask Veeam consider this going forward. As it is, it's a problem when planning for a migration to Proxmox from VMware.

Statistics: Posted by MrGrim — Oct 18, 2025 6:39 am

---