RHEL is a subscription, not a perpetual license
The RHEL code itself is open source — you don't buy a "license" in the Windows sense. You pay Red Hat for a subscription: access to updates and security patches, technical support, hardware/application (ISV) certifications and management tooling. Without an active subscription the system still runs, but you lose updates and support — and formally you aren't entitled to use Red Hat's repositories.
subscription (no perpetual)
socket pair / host
Standard, Premium
That's a fundamental difference from Windows Server: there a perpetual license lets you run a version "indefinitely", with support/patches over the lifecycle. RHEL is fully subscription-based — stop paying and you stop receiving updates.
The subscription on a dense Proxmox host
The key cost decision is how many RHEL VMs you run on a host:
| Subscription type | What it covers | Effect on Proxmox |
|---|---|---|
| RHEL Server (per-socket) | Standard and Premium: 1 host up to 2 CPU sockets or up to 2 VMs. Self-support: physical system only, no guests | every ~2 RHEL VMs needs another subscription |
| RHEL for Virtual Datacenters | a host socket pair — unlimited RHEL guests on that host | one subscription covers all RHEL VMs on the node |
Analogous to the "density trap": under per-socket, every pair of RHEL VMs is another subscription. On a node with a dozen-plus RHEL VMs, Virtual Datacenters (unlimited guests per socket pair) is almost always cheaper — it's the equivalent of Windows Datacenter.
In an HA cluster the model decides what the subscription covers. With RHEL Server you count guests (VM count ÷ 2) and move the subscription with the VM — you do not pay for every node merely because the guest might land there. With RHEL for Virtual Datacenters the unit is a physical socket pair, so every node the guest can run on needs its own subscription.
Red Hat catalog prices
Below are indicative annual Red Hat catalog prices (1-year subscription). Resellers and multi-year deals usually discount (typically 15–35%), so treat this as a budgeting reference point.
| Subscription | Scope | Catalog price / year (USD) | Approx. (PLN) |
|---|---|---|---|
| RHEL Server — Self-support | physical system up to 2 sockets only, no guests and no SLA | ~$384 | ~1,540 zł |
| RHEL Server — Standard | host up to 2 sockets / 2 VMs, 8×5 support | ~$879 | ~3,520 zł |
| RHEL Server — Premium | host up to 2 sockets / 2 VMs, 24×7 support for Sev 1–2 issues (Sev 3–4 during business hours) | ~$1,429 | ~5,720 zł |
| RHEL for Virtual Datacenters — Standard | socket pair, unlimited guests, 8×5 | ~$3,024 | ~12,100 zł |
| RHEL for Virtual Datacenters — Premium | socket pair, unlimited guests, 24×7 for Sev 1–2 issues | ~$4,839 | ~19,400 zł |
Example — a 2-socket node with 10 RHEL VMs. Per-socket Standard: 10 VMs ÷ 2 = 5 subscriptions × $879 = ~$4,395/yr. Virtual Datacenters Standard: ~$3,024/yr for any number of RHEL guests on that node — and the more VMs, the bigger the VDC advantage.
Prices are indicative, converted at ~4 zł/USD; Red Hat publishes the list in USD, and real rates depend on channel, discounts and contract length. Subscriptions may also be counted differently for large/multi-socket hosts — confirm your scenario with a Red Hat partner.
What to choose
- Many RHEL VMs on a node → RHEL for Virtual Datacenters: one subscription per socket pair, unlimited guests — after the Proxmox scope is confirmed (virt-who section).
- A few RHEL VMs → RHEL Server per-socket (Standard or Premium per the SLA you need).
- ISV certifications / critical SLA → RHEL Premium (24×7 for Sev 1–2 issues) on the machines that truly need it.
- HA cluster → with RHEL Server, move the subscription with the guest; with Virtual Datacenters, cover every node the VM can move to with a socket pair.
Red Hat's models and prices change over time — confirm your specific scenario and current rates with a Red Hat partner. The above are general rules and indicative prices, not commercial or legal advice.
Interested in licensing Windows VMs on the same cluster? See Windows Server licensing on Proxmox VE — the per-core model, Datacenter, per-VM and 2025 prices.
Does RHEL for Virtual Datacenters run on Proxmox
A Red Hat Enterprise Linux guest on Proxmox VE runs. Proxmox VE uses KVM/QEMU, so the system installs and operates normally. The RHEL for Virtual Datacenters subscription is a separate question: Red Hat describes it as unlimited guests on supported hypervisors.
The list covers Red Hat platforms — OpenShift Virtualization, Red Hat OpenStack, Red Hat Virtualization and RHEL with KVM — plus VMware ESXi, Microsoft Hyper-V and Nutanix AHV. Proxmox VE is absent from that list. Guests attach to the Virtual Datacenters pool only after the hypervisor reports itself to Red Hat through the virt-who agent. There is no official virt-who connector for Proxmox.
Support and entitlement. Product Appendix 1 withholds Red Hat technical support when the software runs outside a Supported Configuration. That is a support exclusion. Use outside the supported case requires purchasing the subscription that matches the actual deployment.
A manual virt-who file
Where a connector is missing, some organisations report hosts with a manual virt-who file — an inventory of hypervisor and guest identifiers. The file itself does not breach the agreement when it describes the actual deployment: Proxmox node identifiers, socket counts and RHEL guest identifiers.
A file that understates the deployment is a breach. Appendix 1 treats partial coverage of units, and splitting one subscription across more hosts than it covers, as unauthorised. The Virtual Datacenters unit is a physical socket pair, not a VM count.
- A cluster node left out — a VM can land on an unsubscribed host during live migration or failover.
- Under-counted sockets — the server has more processors than the file reports.
- A guest mapped to the wrong host — the VM identifier points at a node where that system is not running.
A defensible layout. Every Proxmox node a RHEL guest can land on has a paid Virtual Datacenters socket pair, with the same support level across the cluster. The virt-who file reports exactly those nodes and those guests. Confirm the Proxmox scope in writing with a Red Hat partner or account team: the subscription guide limits Virtual Datacenters to supported hypervisors, and the appendix remains the binding document.
Without that confirmation, use RHEL Server per guest (up to two VMs per subscription). The guest registers itself, virt-who is unnecessary, and the hypervisor can sit outside Red Hat's list.
This summarises the general terms in Product Appendix 1 and the Red Hat subscription guide. It is not legal advice. Confirm a Virtual Datacenters purchase for a Proxmox cluster with a Red Hat partner before you buy.
Do Red Hat tickets cover Proxmox
Red Hat does not support Proxmox. The subscription covers help for the Red Hat Enterprise Linux guest. Proxmox VE is not on the certified-hypervisor list, which includes RHEL with KVM, OpenShift Virtualization, VMware ESXi, Microsoft Hyper-V and Nutanix AHV. Red Hat has no joint-support agreement with Proxmox of the kind it has with VMware or Microsoft.
Red Hat does not take bugs in Proxmox itself, in Proxmox's QEMU build, or in host-side storage and networking. Those tickets go to Proxmox support.
| Where the cause sits | What Red Hat does |
|---|---|
| A bug in RHEL itself | Red Hat works a ticket for a fault in RHEL itself, such as a package, the guest kernel, an erratum, or subscription registration. Proxmox is not the cause. |
| A suspected hypervisor issue | Red Hat asks for a reproduction on bare metal or on a certified hypervisor. A reproduction that exists only on Proxmox is not enough for a Red Hat fix. |
| A cause inside Proxmox | Red Hat closes the case as an unsupported configuration. Proxmox support takes it from there. |
Product Appendix 1 withholds help for Red Hat software on a platform outside a supported configuration, and for third-party infrastructure. The Customer Portal adds that, for virtualization off the certified list, support will make a reasonable attempt to diagnose the guest and then hand the topic to the hypervisor vendor. That is not full production support for the RHEL and Proxmox pair.
We'll size RHEL licenses for your cluster
We'll plan the optimal subscription model — per-socket or Virtual Datacenters — so the cost is as low as possible while keeping support and compliance.
⚡ Free consultation → Windows Server licensing