Leaving VMware just got harder after Broadcom pulled VDDK downloads
269 points
• 6 days ago
• Article
Link
Broadcom 已悄然撤下对 VMware Virtual Disk Development Kit（VDDK）的公开访问，这给试图将工作负载从 vSphere 迁出的组织带来了重大障碍。 VDDK 是许多行业标准工具（包括 Microsoft Azure Migrate 、 Red Hat 的 Migration Toolkit for Virtualization 和 Nutanix Move）用来完成数据传输和平台迁移的关键库。 Broadcom 限制这些文件的获取，实际上让许多 VMware 客户的退出方案变得更加复杂。
这些下载页面是在没有任何正式公告或替代方案提示的情况下被移除的。尝试访问原先链接的用户现在会遇到 404 错误，且有报告称 Broadcom 的支持明确告知客户该套件不再对公众开放，并将用户引导至其授权的备份与恢复合作伙伴，这表明 VMware 相关技术正被更严格地管控和限制访问。
主要厂商已开始调整应对策略，Microsoft 和 Red Hat 等公司已更新技术文档以反映这一变化。 Microsoft 建议在无法获取 VDDK 时采用基于代理的迁移方案；Red Hat 则表示由于该库为专有软件，他们无法自行托管或重新分发。这些调整说明这并非网站临时故障，而是一次影响广泛迁移流程的有意政策性变动。
不过，部分平台不受此限制影响。例如，Proxmox 内置的导入工具并不依赖 VDDK，用户仍可在不获取外部 VMware 库的情况下迁移 VMDK 。然而，对那些严重依赖 VDDK 的第三方工具用户来说，迁移流程已明显变得更繁琐。组织现在需要直接从 Broadcom 获取授权（可能需要加入特定技术计划），或寻找完全不同且可能更复杂的迁移方案。
Broadcom has quietly removed public access to the VMware Virtual Disk Development Kit, commonly known as the VDDK, creating a significant new hurdle for organizations attempting to migrate their workloads away from the vSphere platform. The VDDK is a critical library used by numerous industry-standard tools, including Microsoft Azure Migrate, Red Hat's Migration Toolkit for Virtualization, and Nutanix Move, to facilitate data transfers and platform transitions. By restricting access to these files, Broadcom has effectively complicated the exit strategy for many VMware customers.
The removal of these download pages has occurred without a formal announcement or a clear replacement path. Users attempting to access previously available links now encounter 404 errors, and reports indicate that Broadcom support has explicitly informed customers that the kit is no longer available for general use. Instead, support representatives have directed users toward authorized backup and recovery partners, further signaling a shift toward a more restricted, gatekept environment for VMware-related technologies.
Major vendors are already reacting to the fallout, with companies like Microsoft and Red Hat updating their technical documentation to reflect the lack of public availability. Microsoft now advises administrators to shift to agent-based migration methods when the VDDK is inaccessible, while Red Hat has acknowledged that because the library is proprietary, they cannot host or redistribute it themselves. These updates confirm that the change is not a temporary website glitch but a deliberate structural adjustment that impacts widespread migration workflows.
Despite the disruption, some platforms remain unaffected by this specific restriction. For instance, the import utility built into Proxmox does not rely on the VDDK to move VMware workloads, allowing users to continue migrating VMDKs without needing to source external VMware libraries. However, for those heavily reliant on third-party utilities that depend on the VDDK, the migration process has become significantly more cumbersome. Organizations are now faced with needing to secure direct authorization from Broadcom, which may involve membership in specific technology programs, or finding entirely different, potentially more complex, migration strategies.
158 comments • Comments Link
Broadcom 收购 VMware 普遍被视为典型的 Avago-style 操作：并购成熟的现金牛业务，通过大幅削减成本和提高价格来榨取短期利润，而非依靠创新。
许多长期员工和工程师感叹，VMware 的衰落始于内部自满——高层把市场主导地位当成理所当然且持久不变，结果错失机遇、人才大量流失。
向复杂许可与定价模式的转变，加速了客户寻找替代方案的步伐。许多 IT 专业人士正转向 KVM 、 Hyper-V 或 Proxmox，以摆脱供应商锁定。
尽管 Proxmox 和类似平台正变得日益可行，业内对其可替代性的看法仍不一致。企业环境通常需要 VMware 长期提供的大规模管理功能、强有力的支持以及成熟的生态系统，这些并非简化版桌面 hypervisor 能轻易取代。
迁移项目往往由财务动因驱动，但也暴露出显著摩擦点：定制化工具、存储管理和遗留应用的依赖仍深度耦合在 VMware 技术栈中，迁移成本和复杂度不容小觑。
大型企业偏好专有解决方案，通常源于风险厌恶和对"可替代性"的追求——企业更愿意采用标准化、由厂商支持的工具，以简化招聘并把运营责任转嫁给供应商。
相比之下，构建定制化的内部基础设施被视为大公司更为优越的长期策略，因为它可以消除对许可的依赖并实现高度定制化，但这需要对员工技能长期投入，而许多现代企业文化并不具备这种耐心和投入。
对 Broadcom 策略的不满，激发了社区关于保存遗留软件以及开源替代方案最终是否能超越传统虚拟化巨头的讨论。
此外，"VMware Workstation"（面向消费者 / 桌面）与 "vSphere/ESXi"（面向企业数据中心）之间的差异常常被混淆。基础设施专家指出，企业级技术栈的复杂性远非桌面 hypervisor 的简化版本可以轻易复制。
激进的资产提取经济模式经常被批评为寄生式，但自由市场的支持者认为，这是一种不幸但可接受的权衡，因为在其他方面该体系也催生了高水平的创新。
总体来看，这些讨论反映了人们对老牌软件公司金融化的广泛沮丧：为了股东回报，客户需求和工程完整性被牺牲。许多人承认 VMware 曾经是一款定义虚拟化时代的卓越产品，但向高成本、提取式模式的转变，从根本上侵蚀了将大型企业绑定在该平台上的信任。在追求开源解决方案（如 Proxmox）所带来的控制权和成本效率，与企业风险管理（通常要求供应商合同保障）之间存在明显张力。最终，这暴露出一个技术依赖的恶性循环：那些没有为长期独立性做规划的公司，最终会发现自己被商业模式已不再以客户成功为中心的供应商所束缚。 • Broadcom's acquisition of VMware is widely viewed as a classic "Avago-style" play, where a cash-cow business is acquired to maximize short-term profits through aggressive cost-cutting and pricing increases rather than innovation.
• Many long-term employees and engineers lament that VMware's decline began with internal complacency, where leadership viewed market dominance as an assured, permanent state, leading to missed opportunities and talent attrition.
• The shift toward complex licensing and pricing has accelerated the search for alternatives, with many IT professionals migrating to KVM, Hyper-V, or Proxmox to escape vendor lock-in.
• While Proxmox and similar platforms are increasingly viable, professional sentiment remains divided, as enterprise environments often require the large-scale management features, robust support, and specialized ecosystems that VMware historically provided.
• Migration projects are often driven by financial necessity, yet they expose significant friction, as custom tooling, storage management, and legacy application dependencies remain deeply integrated with the VMware stack.
• The preference for proprietary solutions in large enterprises is frequently rooted in risk aversion and the desire for "fungibility," where corporations prioritize standardized, vendor-supported tools to simplify hiring and offload operational responsibility.
• Building custom, in-house infrastructure is often cited as a superior long-term strategy for large companies, as it eliminates license dependencies and allows for perfect customization, though it requires a long-term commitment to staff expertise that many modern corporate cultures lack.
• Discontent with Broadcom's strategy has spurred community discussions regarding the preservation of legacy software and the potential for open-source alternatives to eventually surpass the capabilities of traditional virtualization incumbents.
• The contrast between "VMware Workstation" (consumer/desktop) and "vSphere/ESXi" (enterprise data center) is a frequent point of confusion, with professional infrastructure users noting that the enterprise stack involves a complexity level that simplified desktop hypervisors cannot easily replicate.
• The economic model of aggressive asset extraction is often criticized as parasitic, yet proponents of free-market enterprise argue that such outcomes are an unfortunate but acceptable trade-off for a system that otherwise fosters high-level innovation.
The discourse reflects a broader frustration with the financialization of established software companies, where the needs of customers and the integrity of engineering are sacrificed for shareholder returns. While many acknowledge that VMware was a genuinely superior product that defined an era of virtualization, the shift toward a high-cost, extractive model has essentially shattered the trust that kept large enterprises tethered to the platform. There is a palpable tension between the desire for the control and cost-efficiency of open-source solutions like Proxmox and the reality of enterprise risk management, which often mandates the safety of a vendor contract. Ultimately, the situation highlights a cycle of technological dependency where companies that fail to plan for long-term independence find themselves trapped by vendors whose business model no longer includes the success of the customer.