Broadcom–VMware: perpetual licences are going away. What should you do with your ESXi servers?

On 22 November 2023, Broadcom completed its acquisition of VMware, and barely three weeks later, on 11 December, it announced the first major change: VMware products – including vSphere and VMware ESXi – can now only be bought as subscriptions. Sales of perpetual licences have ended, and the support contracts for existing perpetual licences (Support and Subscription, SnS) can no longer be renewed either.

This affects almost every company that runs VMware on its own servers. In this article we sum up what we know now, what it means for existing environments, and which options you can choose from.

What did Broadcom announce?

According to the 11 December post by the head of the VMware Cloud Foundation division and the accompanying FAQ:

  • No more perpetual licences. New purchases are only possible with subscription (or term) licences.
  • No SnS renewal for perpetual licences. Broadcom will honour support contracts already signed until they expire, but they cannot be renewed.
  • A simplified product line-up. The main offering is VMware Cloud Foundation (VCF), the complete private cloud package. The new offering aimed at medium-sized and smaller clients is VMware vSphere Foundation (VVF), which bundles vSphere with operations management tools. For more limited needs, vSphere Standard and vSphere Essentials Plus remain available.
  • Exchange programme. Owners of perpetual licences can switch to a subscription at a discount, and they don’t have to give back their old licences.
  • Prices. According to Broadcom, the subscription list price of VCF has been cut in half. The announcement says nothing about the prices of the other packages, or about how much the switch will cost a given client.

In these first days there is still a lot of uncertainty: partners and clients are still trying to find out what will happen to the smaller packages that have been popular so far, and to the actual prices. Further details and changes are expected in the coming months.

What does this mean for existing VMware ESXi servers?

Your servers won’t stop. A perpetual licence remains valid, and ESXi and vCenter keep running just as before.

Support, however, will have an expiry date. As long as your SnS contract is valid, you get support and access to updates. After that you can’t renew it: you either switch to a subscription or you are left without support and new fixes. For a hypervisor this is a serious risk, because all your virtual machines run on it.

Version lifecycles don’t stop either. Under current plans, general support for vSphere 7 ends on 2 April 2025, and support for the 6.5 and 6.7 branches already ended in October 2022. Anyone running version 7 with a perpetual licence now has two decisions to make: the upgrade and the licensing model.

The free ESXi (vSphere Hypervisor) was not mentioned in the 11 December announcement. If you rely on it in a smaller environment, it’s worth watching for further announcements, and it’s not worth planning a new system around it.

First step: an inventory

Before you decide anything, look at exactly what you have:

  1. Licences: which product, which edition (Essentials, Essentials Plus, Standard, Enterprise Plus), for how many processors.
  2. SnS contract expiry dates: these determine how much time you have. If the contract is valid for another year or two, you can plan calmly.
  3. Versions: which ESXi and vCenter versions are running, and how long they are supported.
  4. Features in use: vMotion, HA, DRS, vSAN, distributed virtual switch, backup software integration. These decide what you actually need.
  5. Virtual machines: how many, with which operating systems, how much storage, and how critical each one is.

What are your options?

Stay with VMware, with a subscription

If you use tools built on the VMware ecosystem (backup, monitoring, automation) and your team knows it, switching to a subscription is the least work. Ask your partner for a quote before your contract expires, and calculate the cost over several years. Don’t assume it will be cheaper: the direction of the change clearly points towards larger packages.

Wait while your support lasts

If your SnS is valid for a long time yet, you don’t have to decide straight away. But use this time for planning, not for putting things off: months before the expiry date, you already need to know where you are heading.

Move to another hypervisor

Since the acquisition was announced, many companies have been looking at alternatives. The most common ones:

Platform Licence When is it a good choice?
Proxmox VE Open source, optional subscription Small and medium-sized environments, KVM and LXC containers, built-in clustering, Ceph and ZFS
Microsoft Hyper-V Part of Windows Server If the environment is mostly Windows and you already have the Windows Server licences
XCP-ng Open source (Xen-based) If you want something that works like Citrix Hypervisor
Nutanix AHV Commercial, part of the Nutanix platform For hyperconverged systems, if the Nutanix hardware or platform is already in place
Public cloud Usage-based pricing If you would move some of your servers to the cloud anyway

For small and medium-sized environments we recommend Proxmox VE; we wrote about it in detail earlier. Proxmox VE 8.1, released on 23 November 2023, now supports Secure Boot, software-defined networking (SDN) is no longer experimental, and Ceph Reef is supported. In our article on the release of Proxmox VE 8.0 we also summed up the other new features of the major version. The platform can be used free of charge; the enterprise repository and vendor support require a subscription, which starts at €105 per CPU socket per year.

How can virtual machines be moved from ESXi to Proxmox VE?

Moving a few dozen virtual machines is a task that can be planned well. The main steps:

  1. Preparation on the source machine. On Windows, install the VirtIO drivers in advance so that both the disk and the network card work in the new environment. Write down the network settings.
  2. Export. Shut down the virtual machine and export it to OVF format, or copy the VMDK disk files to the Proxmox host.
  3. Import on Proxmox VE. From the OVF export, the qm importovf command creates the virtual machine in one step, and qm disk import adds the VMDK disk to an existing machine:

    qm importovf 120 /mnt/export/webserver/webserver.ovf local-lvm
    # or to an existing VM 121:
    qm disk import 121 /mnt/export/db/db.vmdk local-lvm
    
  4. Follow-up work. Remove VMware Tools, install the QEMU guest agent, check the name of the network card (it may change on Linux), and test the application.
  5. Cutover. For critical machines, in a maintenance window agreed in advance, leaving the old machine untouched for a while so that you can roll back if needed.

It’s also worth rethinking the storage of the new environment at this point: in our article on RAID levels we summed up which layout is good for what, including ZFS.

What’s worth doing now

  1. Take an inventory of your licences, contract expiry dates and the features you use.
  2. Ask for a quote for the subscription, so that you have something to compare against.
  3. Try out an alternative in a test environment, with a few non-critical virtual machines.
  4. Make a decision well before your SnS expires, and prepare a scheduled migration plan.

We help with planning and carrying out the move from VMware to Proxmox VE, and with operating Proxmox clusters; you can read more about this on the Infrastructure and operations page.

Let’s talk about your project

Tell us briefly how we can help, and we will get back to you as soon as we can.

Get in touch