In a move that speaks to the anxieties of a platform sensing its own erosion, VMware has quietly removed public access to a software toolkit that competitors and integrators have long used to help customers move away from its ecosystem. The company frames the restriction as a licensing clarification — migration use, it says, was never permitted — yet it watched that use flourish for years without objection. What looks like a policy correction reads, in context, as a quiet toll booth erected at the exit.
VMware cuts off free VDDK access, blocking rival migration tools
A vendor is entitled to change. Doing it without a word is something else.
Mark
So VMware just removed something people were using to leave VMware. That seems pretty direct.
Mimi
It is direct, but VMware's argument is that people were using it for something it was never licensed for. They say VDDK was always meant for backup and recovery only.
Luke
But they let it be downloadable for years without saying that. If it was never supposed to be used for migrations, why didn't they say so earlier?
Mimi
That's the thing. They didn't police it. Nutanix, Red Hat, all these companies built migration tools around it. VMware watched it happen.
Mark
So this is about locking people in?
Mimi
It's part of a pattern. VMware's licensing has gotten stricter. Some of their own partners are already thinking about moving away.
Luke
How much does this actually matter though? Can people still migrate without VDDK?
Mimi
Yes. Smaller integrators have found workarounds. But it adds friction—cost, time, complexity.
Mark
For who exactly?
Mimi
For the people with the least leverage. A big backup vendor has a relationship with VMware, someone to call. A three-person consultancy or an open-source project just hits a 404.
Luke
And VMware says it's all still available through their partners if you have the right agreement.
Mimi
Right. But that's not the same as public access. It's controlled access now.
Mark
Does this actually stop people from leaving?
Luke
Probably not. Moving VMs is the easy part. The hard part is rebuilding everything else—networks, security, storage. VMware knows that. That's why they have their own migration tool.
Mimi
So it's more about making the exit slightly more painful than actually preventing it.
Le Pouls
- VMware pulled its Virtual Disk Development Kit from public download without warning, leaving installation guides across the internet pointing to dead links.
- Competitors like Nutanix and Red Hat, along with smaller integrators and open-source projects, built migration workflows around this toolkit — those pipelines are now disrupted mid-project.
- VMware's defense — that migrations were never a licensed use case — strains credibility given years of silent tolerance while rivals built entire tools around the SDK.
- The restriction lands inside a broader pattern of licensing pressure that has already prompted major channel partners like Rackspace and Macquarie Telecom to publicly reconsider their VMware commitments.
- Workarounds exist and VM movement is only one layer of a full platform migration, so the practical ceiling on damage is real — but the friction is deliberate, and the message is clear.
In a move that speaks to the anxieties of a platform sensing its own erosion, VMware has quietly removed public access to a software toolkit that competitors and integrators have long used to help customers move away from its ecosystem. The company frames the restriction as a licensing clarification — migration use, it says, was never permitted — yet it watched that use flourish for years without objection. What looks like a policy correction reads, in context, as a quiet toll booth erected at the exit.
VMware has quietly removed public access to its Virtual Disk Development Kit — a software library developers have long used to move virtual machines between platforms — without announcement or explanation. The company's subsequent defense was that the toolkit was never licensed for migration use, only for backup and recovery.
The VDDK's versatility made it a quiet cornerstone of the competitive landscape. Nutanix embedded it in its Move migration tool. Red Hat recommended it for migrations. ShapeBlue, an Apache CloudStack integrator, noted that the virt-v2v engine powering most VMware-to-KVM conversions depends on it as a transport layer. For years, the toolkit sat freely available, and VMware raised no objection.
When the download pages vanished in late August, ShapeBlue noticed within days. Its response was measured but pointed: a vendor may change how it distributes an SDK, but doing so silently — while guides across the internet still direct users to links that now return 404 errors — is a different matter. The burden falls unevenly. A large backup vendor with a formal partnership has someone to call. A small consultancy or open-source project gets a forum post and a dead link.
VMware told The Register that access remains available through select technology alliance partners, but only for licensed backup and recovery use. Migrations, the company argued, were never covered. The toolkit is a developer license, VMware added, separate from any Broadcom software purchase.
The timing fits a broader pattern. VMware's recent licensing changes have already pushed channel partners like Rackspace and Macquarie Telecom to publicly weigh reducing their platform reliance. The VDDK restriction arrives as part of that same pressure — and VMware's claim that migration use was never intended rings hollow given years of silent acquiescence.
The practical impact may be limited. Moving virtual machines is among the simpler parts of a full migration; rebuilding networks, security policies, and storage infrastructure is the harder work. Smaller competitors have already found workarounds. The restriction will slow some projects and frustrate some teams, but it is unlikely to stop anyone seriously committed to leaving. What it does accomplish is make the exit slightly more difficult, slightly more expensive, and slightly more dependent on VMware's own tools.
VMware has quietly shut down public access to its Virtual Disk Development Kit, a software library that developers have relied on for years to move virtual machines between platforms. The company removed the download pages without announcement or explanation, then defended the decision by arguing that the toolkit was never meant to be used for migrations in the first place—only for backup and recovery work.
The VDDK is a collection of libraries and utilities that lets software developers build applications capable of accessing and manipulating virtual disks. It handles backup, recovery, cloning, and other disk operations. That versatility made it invaluable to VMware's competitors. Nutanix built it into its Move migration tool. Red Hat recommends it for migrations. ShapeBlue, an integrator specializing in Apache CloudStack, noted that the virt-v2v engine powering most VMware-to-KVM conversions depends on VDDK as a transport layer. For years, the toolkit sat there, freely downloadable, and VMware said nothing.
Then, in late August, the download pages vanished. ShapeBlue discovered the change a day or two after it happened. The company's response was measured but pointed: a vendor can certainly change how it distributes an SDK, but doing so silently while installation guides across the internet still direct people to a link that returns a 404 is something else entirely. The burden falls unevenly too. A large backup vendor with a formal partnership has someone to call. A three-person migration consultancy, a small open-source project, or a customer handling their own workload gets a forum post and a dead link.
VMware's defense rested on a distinction between licensed and unlicensed use. The company told The Register that VDDK access remains available through select technology alliance partners—the term VMware uses for third-party developers in its ecosystem—but only for the licensed use case of backup and recovery. Migrations, VMware argued, were never a covered use. The toolkit is not a customer entitlement, the company added. It is a developer license, separate from any Broadcom software purchase, and was never bundled with VMware products.
The timing of the move sits within a broader pattern of licensing friction. VMware's recent policy changes have already pushed some customers to consider scaling back their use of the platform. Rackspace and Macquarie Telecom, both VMware channel partners, have publicly weighed reducing their reliance on the company's products. The VDDK restriction arrives as part of that same pressure.
Yet VMware's claim that migrations were never an intended use case rings hollow. The company has watched competitors build migration tools around VDDK for years without objection. It is difficult to imagine VMware was unaware of how the SDK was being used. The sudden enforcement of a licensing boundary that was never previously policed looks less like a clarification and more like a defensive move—an attempt to raise friction for anyone trying to leave the platform.
That said, the practical impact may be limited. Moving virtual machines is one of the simpler parts of a full virtualization migration. The harder work lies in rebuilding networks, security policies, and storage infrastructure across an entire environment. VMware knows this, which is why it offers its own site recovery tool that doubles as a migration utility. Smaller competitors have already found workarounds that allow VM migration without VDDK. The restriction will slow some projects and frustrate some teams, but it is unlikely to stop anyone seriously committed to leaving VMware. What it does accomplish is make the exit slightly more difficult, slightly more expensive, and slightly more dependent on paying for VMware's own tools.
Citations marquantes
Access to the VDDK is still available through select TAP for its licensed use case, which has always been backup and recovery. Customers needing backup and recovery capabilities can choose from the many approved solutions already available from these partners.— VMware spokesperson to The Register
A vendor is entitled to change how it distributes an SDK. Doing it without a word, while the Apache CloudStack administration guide and other projects' install instructions still tell people to click a link that no longer resolves, is something else.— ShapeBlue
Envie de l'histoire complète ?
Lire l'original sur The Register ↗
Technology