Broadcom’s Core Count Rules Are Turning VMware Renewals Into Absurd Theater

There is something uniquely infuriating about being told you cannot meaningfully reduce your VMware bill even after reducing what you actually need. That was the center of a recent March discussion about core-count limits, licensing tiers, and Broadcom’s refusal to let reality behave like accounting. The customer wanted a smaller future footprint. Broadcom’s structure, according to the thread, pointed them toward a bigger, more expensive outcome anyway. That kind of mismatch is where enterprise software starts feeling less like infrastructure and more like satire. When a company using less can still end up paying more, the conversation stops being technical very quickly. ## The Math Feels Designed to Humiliate Buyers One of the thread’s most brutal lines was that a renewal of a smaller number of cores at the higher tier would still cost more than the much larger footprint at the lower tier the year before. You can almost hear the silence that follows a sentence like that in a real budget meeting. A few commenters had already seen versions of the same thing. Reduce hardware. Consolidate. Plan a migration. Try to leave a partial footprint behind for hard-to-move systems. Then discover that the licensing model does not actually reward smaller needs in any intuitive way. At that point the product is no longer merely expensive. It feels adversarial. To be fair, defenders of the packaging logic would say VMware is selling capability classes, not just raw core counts. If the customer lands in a tier with broader features or different lifecycle expectations, maybe the price jump is not as irrational as it first appears. That argument exists for a reason, but it did not land emotionally in the thread. The issue was not whether bundles have logic. The issue was whether the logic maps to how customers are trying to run down their VMware footprint during a transition period. Right now, many of them clearly believe the answer is no. ## Customers Are Trying to Leave Cleanly, Not Cheat the System That point matters. The people in these discussions are often not trying to game VMware. They are trying to reduce exposure responsibly. Keep a smaller environment for the workloads that cannot move yet. Buy time. Avoid a reckless all-at-once migration. In theory, that sounds like exactly the kind of measured enterprise behavior a vendor should support. In practice, customers are reporting the opposite feeling. One anonymous commenter described the whole setup as a pricing model that punishes deceleration. That line sticks because it explains why even calm admins start sounding furious. They are not being reckless. They are being boxed in. A different side of the thread argued that the cleanest response is to accelerate migration and stop trying to preserve a long tail of VMware dependence. That has a certain brutal clarity. If the vendor will not make partial retreat affordable, maybe the right answer is to stop paying for retreat at all. But the problem, as others pointed out, is that many environments are not that tidy. There are always awkward systems, legacy integrations, vendor dependencies, and workloads that lag the rest. Real infrastructure exits happen unevenly. A platform that makes uneven exits economically ugly is effectively taxing reality. ## This Is Why Buyers Talk About Being Trapped Thread after thread, that word keeps hovering nearby even when nobody says it directly. Not trapped because VMware is impossible to replace tomorrow, but trapped because every partial move seems to collide with rules that preserve or inflate spend. That changes how customers interpret everything else. A product retirement no longer looks like portfolio cleanup. It looks like pressure. A tier boundary no longer looks like standard packaging. It looks like leverage. Once enough customers internalize the idea that the vendor is pricing against their desire to shrink, goodwill burns fast. The practical risk for Broadcom is not just that people complain. It is that they start designing their architecture with the explicit goal of never needing this conversation again. That is a powerful motivator. Even if the migration takes two years, the determination hardens the day a finance team realizes that being smaller will not necessarily make them cheaper. At that point, VMware is no longer something the organization wants to optimize. It is something it wants to escape on its own schedule. ## The Real Loss Is Predictability Enterprise buyers can handle high prices better than they can handle warped incentives. If the rule is “use more, pay more,” painful but understandable. If the rule becomes “use less, still pay more, and maybe even move up a tier while you’re at it,” the platform starts violating basic common sense. That is what the March thread captured so well. Not just irritation, but disbelief. The kind of disbelief that lingers after the call ends and makes every future negotiation feel a little more toxic. VMware still has deep technical gravity, and that is why customers keep trying to manage partial exits instead of torching the whole estate in one go. But if the licensing model keeps making rational downsizing look economically irrational, Broadcom may discover that it is teaching customers the exact lesson it should fear most: if staying smaller inside VMware is impossible, then staying at all becomes much harder to defend.