VMware and the operating cost of infrastructure software dependency after Broadcom

VMware and the operating cost of infrastructure software dependency after Broadcom

After Broadcom, VMware continuity is not one licensing question. Operators must keep three records aligned: the entitlement and support path, the running workload and its dependencies, and a tested route to another supported endpoint.

Summary

• Broadcom completed the VMware acquisition, moved the portfolio toward subscriptions, and migrated VMware support operations into Broadcom systems.
• VCF license portability can protect an eligible subscription across supported endpoints, but eligibility and provider conditions mean it is not a universal right and it does not move a workload by itself.
• The Heng.lu Doctrine test is running-code continuity: inventory entitlements, dependencies, storage, network mappings, support identities, migration validation, cutover, and rollback before treating the platform as portable.

The dependency now has three operational records

Broadcom completed its acquisition of VMware on November 22, 2023. The important operating consequence is not the transaction headline by itself. VMware estates now depend on three records that can drift apart: the commercial record showing what the customer may run and where, the support record showing who can obtain downloads and open cases, and the technical record showing which workloads, storage systems, networks, backup tools, and recovery procedures still depend on the platform.

Broadcom's December 2023 announcement completed the shift toward subscription and term licensing, ended new perpetual-license sales and perpetual Support and Subscription renewals, and told existing customers to review license inventories, renewal dates, and refresh cycles. That instruction is an operator-continuity requirement in practical form. A platform cannot be governed from memory when its rights, versions, and support paths can expire on different dates.

License portability is one layer, not the whole move

Broadcom's VCF portability entitlement is material. For eligible VCF 5.1-or-later subscriptions bought after December 13, 2023 through the specified end-user channels, Broadcom says the customer can deploy the subscription to compatible on-premises, hosting-provider, cloud-provider, or hyperscaler endpoints. The customer remains the licensee, and provider participation plus hardware compatibility still matter.

Those conditions define the boundary. License portability answers whether an eligible subscription may follow the customer to a supported endpoint. It does not answer whether the application's data can be copied in time, whether the destination network preserves required addresses and policies, whether backup and monitoring integrations work, or whether a non-VMware target can accept the workload. Public copy must not collapse commercial permission and executable migration into one promise.

Support identity is part of continuity

Broadcom's support FAQ records the May 2024 migration of VMware portals, tools, and assets into the Broadcom Support Portal. Licenses, downloads, cases, notifications, entitlements, and escalations now depend on Broadcom account roles and Site IDs. That makes support identity an infrastructure control rather than an administrative afterthought.

An operator should be able to prove which people hold portal access, which Site IDs expose the required entitlements, which teams receive critical alerts, and how a severe case is opened if the normal administrator is unavailable. The public documentation does not prove that any named customer lost access. It does prove that a continuity plan which ignores portal identity and entitlement visibility is incomplete.

Workload mobility has a running-code bill

Broadcom's HCX API documentation describes workload mobility across vSphere and VCF environments through vMotion, bulk migration, replication-assisted migration, and planning functions. The same documentation makes the retained work visible: source and destination sites, compute targets, datastores, storage profiles, network mappings, service mesh, appliances, and validation all have to be prepared.

This is the real operating cost of portability. A migration plan needs workload inventory, dependency mapping, capacity at the destination, network and security-policy translation, backup verification, a cutover window, health criteria, and a tested reversal path. The tooling can support those steps; it cannot replace the decisions or prove that a specific workload will meet its recovery objective.

Running-code primacy turns portability into a test

The doctrine gate should therefore ask what continues to run, not which portability label appears in a product announcement. Can the customer still retrieve the required software and open a support case? Can the destination accept the licensed stack? Can the workload move with its data and network state? Can monitoring and backup detect a failed cutover? Can the old site resume operation without corrupting data or identity?

A useful VMware review records each answer and its evidence. The license inventory names rights and dates. The support inventory names accounts, Site IDs, and escalation owners. The technical inventory names virtual machines, storage, networks, integrations, recovery objectives, and rollback state. When those ledgers agree, the operator has continuity. When they do not, familiarity with VMware can hide a dependency that is not yet portable.

What the public record does not prove

The cited record does not establish any customer's renewal price, contract dispute, migration duration, outage, support response, private architecture, or successful exit. It also does not show that VCF portability applies to every VMware product, legacy license, OEM arrangement, embedded use, or provider-obtained entitlement.

The defensible conclusion is narrower. After Broadcom, VMware operators need a current, testable record of entitlement, support identity, workload dependencies, destination eligibility, migration validation, and rollback. That is the operating cost of continuity, and it is the difference between a portable subscription and a platform that can actually move.

Claims To Exclude

• all VMware customers experienced price increases
• Broadcom ended every form of perpetual-license use
• all VMware or VCF licenses are portable
• license portability guarantees workload, data, network, or application portability
• HCX proves migration to an unrelated hypervisor
• every customer lost support or entitlement access during the portal transition
• VMware licenses or Site IDs are equivalent to IPv4, ASN, or RIR registry records
• the public sources prove a specific customer migration cost, outage, or support failure

Source Register

• Broadcom Completes Acquisition of VMware: https://investors.broadcom.com/news-releases/news-release-details/broadcom-completes-acquisition-vmware (Broadcom completed its acquisition of VMware on November 22, 2023; the post-Broadcom operating context is tied to a completed transaction rather than a proposed deal)
• VMware by Broadcom Dramatically Simplifies Offer Lineup and Licensing Model: https://news.broadcom.com/cloud/vmware-by-broadcom-business-transformation (the transition to subscription and term licensing; the end of sale of new perpetual licenses and perpetual Support and Subscription renewals; the reduction of the primary offer lineup)
• Unleashing The Power of VMware Cloud Foundation: New License Portability Entitlements Explained: https://blogs.vmware.com/cloud-foundation/2024/06/04/license-portability-vmware-cloud-foundation/ (eligible VCF subscriptions can move among compatible on-premises, hosting-provider, cloud-provider, and hyperscaler endpoints; customers remain the VCF licensee and retain license-compliance responsibility; the entitlement applies to specified VCF 5.1-or-later end-user subscriptions purchased after December 13, 2023)
• VMware to Broadcom Support Frequently Asked Questions: https://knowledge.broadcom.com/external/article/278681/vmware-to-broadcom-support-frequently-as.html (VMware support portals, tools, and assets migrated to the Broadcom Support Portal on May 6, 2024; license, download, case-management, entitlement, notification, and escalation tasks now depend on Broadcom portal roles and Site IDs; operators must preserve account, entitlement, and support-path continuity as part of platform operations)
• HCX Workload Migration APIs: https://developer.broadcom.com/xapis/hcx-workload-migration-apis/latest/ (HCX exposes vMotion, bulk, replication-assisted, and migration-planning capabilities across vSphere and VCF environments; migration requires source and destination sites plus compute, storage, and network configuration; network extension, network profiles, service mesh, and appliance management are part of workload mobility)