Infrastructure September 8, 2026 bearish ⇧ 222 pts across 1 thread

Broadcom's VMware lockdown accelerates Proxmox migration

Broadcom pulled VDDK downloads, making it harder to leave VMware. The HN thread was not sympathetic to Broadcom. The dominant reaction was that most companies could have been running Proxmox all along and avoided the licensing nightmare entirely. The fact that VMware-to-Proxmox migrations are explicitly not affected by the VDDK restriction was treated as both a relief and a joke.

This is part of a broader pattern this year of legacy infrastructure vendors tightening screws post-acquisition: higher prices, restricted tooling, fewer exit ramps. Broadcom buying VMware was always going to end here. The HN crowd was largely unsurprised.

The practical counterpoint: enterprise at scale has real migration costs, and 'just use Proxmox' glosses over integration depth with existing tooling, support contracts, and the organizational inertia of large IT shops. But for anyone not yet locked in, the decision calculus is increasingly obvious.


So what?

If you run any VMware in production and haven't started a migration plan, Broadcom has given you another data point. Proxmox is mature enough for most workloads. The cost of starting a migration now is lower than the cost of being further locked in a year from now.

Read these