The roughly $61 billion of acquisition debt sets a non negotiable revenue floor on VMware, and every renewal is an installment against it. Tesco is just the most visible customer trying to negotiate against that arithmetic.
Broadcom's 2023 takeover of VMware was a roughly $61 billion deal, and most of the purchase price was debt. That single financial fact is now the structural reason a UK supermarket chain is in a public fight with one of the largest chip and software companies in the world.
The Register's analysis piece "Lessons from the VMwars" frames the Tesco-Broadcom dispute as a licensing argument about VMware software. The story is more useful when read as a debt-service argument, with VMware customers as the cash flow.
Broadcom did not pay $61 billion to run VMware the way VMware had been run. Chief executive Hock Tan's playbook at CA Technologies and Symantec was the same one now applied to VMware: cut operating costs, kill perpetual licenses, push everything to subscriptions, and raise the effective price per customer. The playbook works because enterprise software carries high switching costs. Customers do not rip out the virtualization layer (the software that lets one physical server act like many) under their SAP, SQL Server, Oracle, and internal applications every time a vendor changes pricing tiers. The pricing power comes from the cost of leaving.
That pricing power is now being tested in public with Tesco. The Register reports Tesco alleging contractual violations and unfair practices, including the revocation of support options and perpetual licenses, and Tesco's court filings describe a massive internal push to exit Broadcom entirely, with the company estimating the migration will finish at the end of 2027. Tesco is a £73 billion ($96 billion) revenue business that has been around roughly seventy years longer than Broadcom. It is not a customer that gets priced out and walks away quietly. It also has a documented history of supplier disputes: a UK regulatory investigation about a decade ago found Tesco had been treating suppliers unfairly, delaying payments, and making unilateral deductions. Tesco apologized, paid costs, and rebuilt its billing. Whether it is the zeal of the reformed or the institutional memory of how to play the game, the same company now treating Broadcom as a counterpart is doing the opposite number on its vendor.
The arithmetic is what makes the bondholder read more honest than the vendor-behavior read. Broadcom financed the deal with roughly $61 billion of debt and has been working to reduce that load from operating cash flows. Every SKU consolidation (a SKU is a distinct product line; consolidating them means collapsing many licenses into fewer, more expensive bundles), every perpetual-to-subscription conversion, and every renewal repriced against a captive customer is an installment on that debt. The cash flow has to come from somewhere. VMware's installed base is the somewhere.
This is the part the trade press tends to underplay. Broadcom is not running the playbook by choice. Broadcom is a leveraged acquirer running the playbook because the capital structure requires it. The behavior is the only behavior consistent with the deal. Customers and UK courts are not negotiating with a company that has optionality on pricing. They are negotiating with a company whose bondholders do not.
The same pattern appeared at CA Technologies and Symantec, where Broadcom cut support, killed product lines, and pushed surviving customers onto subscription tiers. Some customers left, but the revenue per remaining customer climbed fast enough to service the debt. The pattern is now repeating at scale on a much larger installed base.
The Tesco case is not a one-off. The VMware customer pool is large, the switching costs are real, and the next twelve to twenty-four months of VMware renewals are the window in which Broadcom's debt schedule and customer budgets collide. Some customers will pay. Some customers will litigate. Some customers will accelerate migration plans to alternatives such as Microsoft Hyper-V, Nutanix, Red Hat OpenShift Virtualization, or one of the public-cloud-native options. The pool's behavior over that window is what the bondholders are actually underwriting.
The Register's reading is that Broadcom will fold before a courtroom resolution, and the more interesting lesson is the supplier-customer power imbalance writ large: a customer that misreads its lock-in loses, a vendor that misreads its customer loses, and the broader IT industry has lived through enough cycles to know the difference. UK contract law and competition review give Tesco and similar customers a forum to challenge the deal structure, but the broader question is whether the deal structure itself is durable: a leveraged acquirer can extract rent from a captive installed base for a finite number of years before alternatives catch up, and the VMware renewal calendar is the clock. Tesco is the visible case. The renewal pool is the case the bondholders are running.