RHEL Server Is a Socket-Pair. VDC Covers Guests.
You opened a Red Hat licensing URL. Keep it. This page is the catalog: how Red Hat counts a RHEL Server subscription, how Virtual Datacenters (VDC) counts, how add-ons stack, and what Appendix 1 requires you to buy. The host-versus-account check stays at How to check if your Red Hat server is licensed. Paid and free alternatives stay at Paid and free alternatives to Red Hat Enterprise Linux.
That’s the problem.
A list of RHEL hosts is not a position. Physical versus virtual, sockets on one machine versus sockets on two machines, guest density, SLA, and whether an add-on sits on the paper are different objects. Mix them and you either under-cover two one-socket boxes with one pair, or you brief unlimited guests you do not have.
Do not invent a list price. Your number is the quote or the Hybrid Cloud Console inventory in front of you.
What a Red Hat subscription actually is
Red Hat does not sell a perpetual RHEL license. The subscription guide (page dated 21 July 2026): you buy a time-bound subscription. It is access to software, updates, support at a stated SLA, and the Customer Portal. When the term ends, those services end unless you renew. Appendix 1 (posted 5 August 2025): the software itself is under the end-user and open source licenses. Subscription Services are term-based.
Appendix 1 section 1.2(a)(i): while you have a subscription, you purchase the applicable subscriptions in a quantity equal to the total number and capacity of Units from the commencement of your use or deployment. Section 1.2(g) calls it unauthorized use to buy for fewer Units than you deploy, or to split Subscription Services purchased for one Unit across two or more Units. That is the coverage rule. It is not “the host can yum, so we are fine.”
IBM Z and LinuxONE are the documented exception: you entitle the cores used by RHEL (subcapacity), not the entire physical node. The guide and Appendix 1 both state it. The rest of this page is the x86 (and ARM) socket-pair model.
Glossary: socket-pair, stacking, virtual node
Use Red Hat’s words, not spreadsheet folklore. From the subscription guide glossary and Appendix 1 Table 1.1:
| Term | Official meaning |
|---|---|
| Socket | A CPU socket occupied by a CPU. Appendix 1: “a socket occupied by a CPU.” |
| Socket-pair | Up to 2 sockets occupied by CPUs on a system. Two servers with a single occupied socket on each must be entitled separately. You purchase 2 subscriptions, one for each server. |
| Stacking | Buy multiple base subscriptions to cover a multi-socket machine. Base unit is a socket-pair. An 8-socket machine needs 4 base subscriptions. |
| Physical node | A physical system on which you install or execute the software (server, blade, laptop, and so on). |
| Virtual node / virtual guest | An instance of the software executed, in whole or in part, on a VM or a container. |
| Guest | An instance running in a VM on a hypervisor. In the model, a guest is associated with a physical system. |
The live trap: treating “2 sockets = 1 subscription” as if two one-socket servers could share. They cannot. Sample worksheet 1: 10 one-socket systems are 10 subscriptions, not 5. 10 two-socket systems are 10 subscriptions. Two 4-socket systems are 4 subscriptions. Two 8-socket systems are 8 subscriptions.
RHEL Server: one pair on the box, or two virtual nodes
Appendix 1 Exhibit 1.A Table 1: Red Hat Enterprise Linux Server is measured as a Physical Node or Virtual Nodes. Capacity: socket-pair for each Physical Node, or 2 Virtual Nodes.
The guide, “Socket-pair for each physical node or 2 virtual nodes”: each RHEL Server subscription entitles you to use it on a physical node with up to 2 sockets, or 2 virtual nodes regardless of virtual sockets. On-prem or public cloud, the virtual-node count is the guest count, not the host sockets.
Subscription portability (same guide): you may transfer a physical 2-socket subscription to a 2-virtual-instance subscription without contacting Red Hat, and the reverse. Server and its add-ons move across physical, virtual, and cloud without changing terms.
Worked shapes from the guide:
| What you run | What you buy (RHEL Server) |
|---|---|
| One 1-socket physical server | One subscription. It cannot share a pair with another 1-socket server. |
| One 2-socket physical server | One subscription. |
| One 4-socket physical server | Two subscriptions (stack). |
| One 8-socket physical server | Four subscriptions (stack). |
| 20 virtual guests, no VDC | 10 subscriptions (guests divided by 2). |
| Replace two 2-socket boxes with one 4-socket box | Same subscription count. Stacking is designed for that swap. |
Do not invent a crossover price. Density is what picks Server versus VDC, not a folklore “N guests” list-price trigger.
VDC: unlimited guests on the host pair
The guide and Appendix 1: Red Hat Enterprise Linux for Virtual Datacenters is a physical-node, socket-pair subscription with unlimited virtual nodes running on that socket-pair. It is the high-density model.
Official constraints you brief, or you brief the wrong SKU:
- Bought on the host. Count hypervisor socket-pairs, not guests.
- Supported hypervisors named in the guide: Red Hat Virtualization, VMware, Microsoft Hyper-V. Do not invent a hypervisor that is not on the paper in front of you.
- No host OS in the VDC SKU. The guide: this subscription does not include a physical entitlement for Red Hat Virtualization. Appendix 1 Note 1: VDC subscriptions do not include an entitlement for the host operating system. If the hypervisor itself needs RHEL, that is a separate Server (or other) subscription.
- Cluster pooling. When pooling VDC, purchase uniform SLAs for all hosts in a cluster, and all hosts in the cluster must be accounted for, unless the hypervisor can restrict and enforce RHEL workloads on a subset of hosts.
- Stacking still applies. An 8-socket VDC host needs four VDC subscriptions, the same socket-pair math.
Appendix 1 section 1.2(d): you do not request a higher service level than you purchased. If a cluster needs Premium, the nodes in that cluster need Premium.
VDC is not “license two guests and run the rest free.” VDC is “pay the host pair, guests on that pair are unlimited, on a supported hypervisor, with the cluster covered.”
How you confirm a given guest is registered, and whether the account holds enough VDC, is How to check if your Red Hat server is licensed. virt-who is not how you get content under Simple Content Access. The transition article: virt-who is still required for accurate Subscriptions Service charts on types such as RHEL VDC. That is reporting, not attach.
Add-ons follow the same pair
The guide: add-ons follow the same socket-pair model as RHEL Server, and can migrate between physical and virtual the same way. Appendix 1 Table 1.2(b): add-on subscriptions are supported only on active Standard or Premium base subscriptions (not Self-support), with limited developer exceptions. For EUS, ELS, and ELS Long Life on versions those add-ons cover, Appendix 1 section 2.6: you purchase a quantity equal to the total number and capacity of every Unit running those versions.
Name the add-ons Red Hat names. Do not invent SKU codes.
| Add-on (official name) | What the current pages say |
|---|---|
| Extended Update Support (EUS) | 24 months of support from a minor release GA, as an independent stream. Legacy extended support page: included with x86-64 RHEL Server Premium; purchasable as an add-on to Standard, IBM Power LE, and IBM Z. Not on Desktop. From RHEL 9, also purchasable for Workstations. |
| Enhanced Extended Update Support | Additional 24 months (48 months from GA). Guide: RHEL 9 and after. Legacy page: not included with Premium, not for Self-support or Workstation. |
| Extended Life Cycle Support (ELS) | Optional add-on in the extended life phase. Last minor of a major. Guide: certain critical-impact security fixes, selected urgent bug fixes, troubleshooting. Minimum 36 months beyond the 10-year lifecycle. Not with Self-support. RHEL 7 ELS is the current ELS period for that major. |
| High Availability Add-On | Failover between nodes in a cluster. Same subscription model as RHEL. |
| Red Hat Satellite | Current management product. Appendix 1 Exhibit 1.D: “Red Hat Satellite (formerly known as Red Hat Smart Management)”, unit = Managed Node. One entitlement per RHEL unit Satellite manages. Satellite Server / Capsule are the on-prem pieces. |
| Red Hat Lightspeed | The guide: included in every RHEL subscription. Not a separate socket-pair you invent. |
The RHEL life cycle page: beginning with RHEL 9, Red Hat unifies the old EUS / Enhanced EUS / E4S streams as Extended Life Cycle (ELC). ELC is 6 years from GA for eligible even-numbered minor releases. Long-Life (LL) is a renewable annual extension after ELC. Legacy EUS / ELS streams continue through their committed end dates. ELC also replaces ELS beginning with RHEL 8.10 on 1 June 2029. New deployments plan ELC. Do not flatten that into “EUS is dead tomorrow.” Read the paper you hold.
Resilient Storage is listed in the guide and is not supported with RHEL 10. Do not brief it onto a 10 estate.
Do not paste a store price for any of these.
Standard versus Premium is an SLA, not a metric
The metric is still the socket-pair or the virtual-node pair. The SLA is how fast Red Hat answers. Production Support Terms of Service:
| Service | Standard | Premium |
|---|---|---|
| Hours | Standard business hours | Standard business hours, 24×7 for Severity 1 and 2 |
| Channel | Web and phone | Web and phone |
| Cases | Unlimited | Unlimited |
| Severity 1 initial | 1 business hour | 1 hour |
Self-support has no production SLA. Developer no-cost SKUs are self-support unless you buy a paid developer support add-on.
Premium on x86 Server is also how you get EUS included. That is a commercial fact from the guide, not a reason to ignore Standard hosts that never needed a pinned minor.
Developer SKUs are not the estate
Keep these off the production true-up unless the paper really is personal.
Red Hat Developer Subscription for Individuals. FAQ (updated 22 April 2026) and the subscription guide: no-cost, up to 16 physical or virtual nodes, personal use only, not for organizations. Development, testing, or small production. Self-support. One per user account. Bits match paid RHEL. This is not the corporate SAM position.
Red Hat Enterprise Linux for Business Developers. Announced 9 July 2025. Guide: no-cost, self-serve, 25 physical, virtual, or cloud instances per registered user, development and test only (not production). Self-support, with optional paid developer support.
Red Hat Developer Subscription for Teams. Guide: no-cost, unlimited instances for development and test (not production), via Red Hat or partner account representatives, for organizations that already run other Red Hat offerings.
Do not brief the 16-node personal SKU as cover for a corporate VMware cluster. Do not brief Business Developers as production.
Simple Content Access changed attach. It did not change the metric.
SCA is how you consume content. It is not a new way to count sockets. Point the host check at How to check if your Red Hat server is licensed. Keep the dates honest here so this hub does not re-teach the late-2025 error.
SCA article: newly created RHSM accounts defaulted to SCA on 15 July 2022. Enabling SCA for RHSM became one-way in April 2024. Most remaining RHSM accounts moved in October/November 2024 (on/around 25 October 2024). Transition article: on 30 October 2025 RHSM entitlement management was discontinued and remaining users, including Advanced Update Support (AUS), moved to SCA. Satellite 6.15 is the last release that supports entitlement workflows through its lifecycle. 6.16 and later are SCA-only.
Under SCA you no longer attach a pool to a host. Hybrid Cloud Console docs: Subscriptions Inventory is what you own. Subscriptions Usage is what you consume. Inventory UI. The metric this page defines (socket-pair versus VDC versus add-on) is what those two views must be compared against.
What to have this week
Do this before the next Red Hat renewal or “Request to Review”. Produce a coverage pack, not a green yum update.
- Every RHEL instance, physical or virtual. Host, guest, cloud. Developer and no-cost SKUs called out, not mixed into production. Infrastructure Mapper is the topology file.
- Sockets the way Red Hat counts them. Socket-pairs on that machine. Two 1-socket boxes are two subscriptions. Virtual nodes regardless of virtual sockets, or VDC on the host pair with the cluster covered.
- SKU type actually required. RHEL Server, VDC, add-ons (EUS / ELC, ELS, High Availability, Satellite). No invented SKU codes. No pasted store prices.
- Owned quantity, SLA, and expiry from Subscriptions Inventory. LCM is the renewal file.
- A cost-optimal cover for the mix of physical and virtual. Red Hat Deployment Manager maps RHEL deployments to SKUs, applies physical versus virtual coverage, and surfaces the evidence.
Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is “two one-socket servers share a pair” or “the VM is registered so VDC does not matter”, you do not have a Red Hat position.
Picture your procurement director, sixty days out. Finance has this URL bookmarked. A green host is not an account in the money. The number is socket-pairs and virtual nodes against the SKUs you actually hold.
The decision layer, not another RHEL inventory
You already have Satellite, a CMDB, and a Hybrid Cloud Console login. The gap is not another discovery export. The gap is turning that estate into a metric: socket-pairs on one machine, virtual-node pairs, VDC versus Server, add-ons, owned quantity. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. RDM is the RHEL file.
If you are heading into a Red Hat renewal or a review and your current tools still need three weeks to separate two one-socket boxes from one two-socket box, or Server guests from VDC hosts, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.
Do not let the vendor frame this as “just register and you are licensed”. Do not let your own side frame a socket-pair as something two servers can share. The right question is: which metric does this instance consume (physical pair, virtual-node pair, or VDC on the host), and does Subscriptions Inventory cover Subscriptions Usage. That is a data question, not a sales question.
The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
Sources
- RHEL subscription guide (21 July 2026): socket-pair glossary, stacking, 2 virtual nodes, portability, VDC, add-ons, developer offerings, worksheets: https://www.redhat.com/en/resources/red-hat-enterprise-linux-subscription-guide
- Product Appendix 1, NA English (5 August 2025): Unit definitions, total Units, unauthorized split, Exhibit 1.A Server and VDC capacity, Note 1 no host OS on VDC, Satellite formerly Smart Management, add-on base SLAs: https://www.redhat.com/licenses/Appendix-1-NA-English-20250805.pdf
- Red Hat Enterprise Agreements landing: https://www.redhat.com/en/about/agreements
- Simple Content Access (defaults 15-Jul-2022; attach obsolete): https://access.redhat.com/articles/simple-content-access
- Transition of subscription services to Hybrid Cloud Console (30-Oct-2025 entitlement end; Oct/Nov 2024 conversion on/around 25-Oct-2024; Satellite 6.15 last entitlement, 6.16+ SCA-only; virt-who still required for VDC charts; AUS): https://access.redhat.com/articles/transition_of_subscription_services_to_the_hybrid_cloud_console
- Hybrid Cloud Console, managing subscriptions (Inventory vs Usage): https://docs.redhat.com/en/documentation/red_hat_hybrid_cloud_console/1-latest/html/getting_started_with_the_red_hat_hybrid_cloud_console/managing-subscriptions_getting-started
- Subscriptions Inventory UI: https://console.redhat.com/subscriptions/inventory
- Production Support SLA (Standard Sev 1 = 1 business hour; Premium Sev 1 = 1 hour): https://access.redhat.com/support/offerings/production/sla
- RHEL life cycle (ELC unifies EUS / EEUS / E4S from RHEL 9; LL after ELC): https://access.redhat.com/support/policy/updates/errata
- Legacy extended support (EUS included on Premium x86; Enhanced EUS not included; RHEL 7 ELS): https://access.redhat.com/support/policy/updates/errata_legacy
- Developer Subscription for Individuals FAQ (16 nodes, personal, small production): https://developers.redhat.com/articles/faqs-no-cost-red-hat-enterprise-linux
- RHEL for Business Developers announcement (9 July 2025, 25 instances, not production): https://developers.redhat.com/articles/2025/07/09/announcing-self-service-access-red-hat-enterprise-linux-business-developers
Related reading
