Leaving VMware just got harder after Broadcom pulled VDDK downloads
Broadcom has unilaterally pulled the VMware VDDK, an essential tool for migrating virtual machines, effectively making it harder for customers to leave the platform. This move, seen as a deliberate lock-in strategy, has sparked outrage among IT professionals already frustrated by Broadcom's post-acquisition changes. The Hacker News crowd is largely debating alternative hypervisors and lamenting the demise of a once-loved product.
The Lowdown
Broadcom, continuing its controversial stewardship of VMware, has abruptly removed public access to the Virtual Disk Development Kit (VDDK). This seemingly minor change has major implications for organizations attempting to migrate off VMware's vSphere platform, as VDDK is a critical dependency for numerous third-party migration and backup tools. The move is widely interpreted as a calculated effort to create vendor lock-in, adding another layer of frustration for customers contemplating an exit.
- VDDK's Critical Role: The VDDK is a library extensively used by major migration tools, including Microsoft Azure Migrate, Red Hat's Migration Toolkit, and Nutanix Move, to transfer VMs from VMware to other virtualization platforms.
- Sudden Disappearance: Broadcom removed the public download pages without official announcement, leading to 404 errors for vendors and customers alike.
- Confirmation of Intent: Broadcom support representatives have reportedly confirmed that VDDK is "no longer available for use or download" through traditional means, advising customers to seek alternatives through authorized partners.
- Industry-Wide Impact: Both Microsoft and Red Hat have updated their documentation and support articles, acknowledging the VDDK's unavailability and suggesting alternative migration methods. Nutanix customers are also reporting issues with their Move utility.
- Lock-in Accusation: The timing of the VDDK's removal, coinciding with Broadcom's efforts to retain customers, fuels suspicions that it's a deliberate tactic to hinder competitor migration and ensure customer retention.
- Proxmox Exception: Interestingly, migrations to Proxmox using its built-in import utility are unaffected, as Proxmox does not rely on the VDDK.
This development is seen as yet another blow to customer trust in VMware under Broadcom's ownership. While some alternatives remain viable, the broad impact on established migration paths underscores Broadcom's aggressive strategy, pushing more organizations to actively seek non-VMware solutions.
The Gossip
Broadcom's Blunders & Business Bites
Commenters express deep dissatisfaction with Broadcom's management of VMware, viewing the VDDK removal as another in a series of hostile actions designed to lock in customers and stifle competition. Many lament the decline of VMware's once-stellar reputation, with some sharing personal anecdotes of their company's exodus from VMware due to these changes.
Proxmox Praises & Hyper-V Headaches
A significant portion of the discussion revolves around alternative hypervisors. Proxmox is overwhelmingly praised as a viable and often superior open-source option, with many users sharing positive experiences migrating from VMware, noting its simplicity and immunity to the VDDK issue. Hyper-V receives mixed reviews, with some finding it functional but others criticizing its usability and fractured toolset compared to VMware.
Migration Maneuvers & Missing Materials
Users discuss practical workarounds for migrating VMs without the VDDK, such as streaming disk images from live VMs or utilizing agent-based methods. There's also a scramble for obtaining the now-unavailable VDDK, with some users pointing to archive sites or torrents as potential sources, highlighting the desperation caused by Broadcom's sudden action.