VMs

·

·

6 min read

You don't have to replace VMware. You have to survive the bill

Tony Como

COO & Co-Founder, Juno Innovations

An older rack server above a newer server in the same dark rack, both running, one orange status light

ON THIS PAGE

Surviving the VMware bill starts with the renewal date and the size of the increase, not with a plan to move every VM at once. Keep the VMs you have on the hosts they run on, stop adding new ones there, and build new VMs on KubeVirt beside your containers. Orion manages both from one place. A workload leaves vSphere only when you build it fresh on KubeVirt, on a schedule your renewals allow.

What did Broadcom change?

When Broadcom bought VMware in November 2023, it ended perpetual licensing. Every VMware customer now pays an annual subscription whether they want one or not. Most enterprises in CloudBolt’s January 2026 survey saw increases of 25 to 49%. Analysts put the range at 50 to 400%, and AT&T said it faced a 1,050% increase (Network World).

The structure changed along with the price. Broadcom raised the minimum order from 16 to 72 cores, according to its distributor Arrow (The Register), so small deployments pay for capacity they don’t need. Arrow also told customers that a late renewal adds 20% to the first year’s price. It bundled products customers used to license separately into VMware Cloud Foundation, so many customers now pay for components they have no use for.

The result is that you rent what you used to own, on a schedule you didn’t pick, at a price that compounds every renewal. That’s a commercial problem first, and it deserves the same treatment as any other big contract.

Do we have to move every VM off vSphere at once?

No, and trying to is the expensive way to do it. Most of the advice out there says to evaluate KubeVirt, OpenShift Virtualization and Proxmox, pick one, and move your VMs. That skips the hardest part, which is the operating model your team built around VMware over the last decade.

VMware shops usually have a dedicated on-prem team and a separate cloud team, with more teams walled off for each additional environment. Each team has its own tooling and its own way of provisioning. Moving everything at once asks those teams to rebuild habits they spent years building, on a compressed timeline, while production keeps running. Organizations that try it often end up running both stacks in parallel at a cost higher than the original VMware bill.

The cheaper path is to stop growing the estate you want to shrink. Existing VMs stay where they are. New work goes somewhere else. The VMware footprint gets smaller each time a VM is retired or rebuilt, and each renewal gets negotiated against a smaller number.

Where does Orion fit if we keep vSphere for now?

Orion manages the VMs already running on your vSphere and Proxmox hosts, where they run. It inherits them, with no plugin to install, and brokers each user’s connection to them. Those VMs show up next to the rest of your workloads without moving anywhere.

New VMs can run on KubeVirt on the same Kubernetes cluster as your containers. Windows and Linux VMs launch from the same Orion Workspace catalog as a notebook or a container desktop, and users connect over RustDesk or another remote desktop through the VM’s port. A VM nobody needs anymore goes back to the pool instead of sitting idle on a host. We walked through one version of this in running a Windows VM and a Linux AI agent on the same cluster.

Be clear about what Orion doesn’t do. It doesn’t convert or import VMware images, and it doesn’t extend support for a vSphere version that is reaching its end. If you want a workload off vSphere, you build it fresh on KubeVirt, from install media or from a golden image you build there. For a lot of VMs that’s less work than it sounds, because the image is usually a known set of installs on top of Windows or Linux. For some it isn’t worth it, and those can stay on vSphere until they retire.

Is KubeVirt ready for production VMs?

A few years ago KubeVirt came with an asterisk. Production readiness was uneven and enterprise support was thin. Most of that is gone. KubeVirt reached its 1.0 release in 2023, it is a CNCF incubating project, and Red Hat builds OpenShift Virtualization on it.

KubeVirt runs VMs on Kubernetes next to your containers, on the same cluster, with the same scheduling. For new VMs that gives you one operating model instead of two. It also doesn’t have to be all-or-nothing. You can run KubeVirt VMs beside your vSphere estate for as long as the two need to coexist.

What does a sensible order look like?

The organizations handling this well tend to work in three steps.

First, put Orion over what you have. Your vSphere and Proxmox VMs keep running, and users reach them from the same place they reach everything else. At the same time, build a handful of new, non-critical VMs on KubeVirt so your team gets hands-on time with it. This is where you find the surprises, on workloads that don’t matter yet.

Second, send new work to KubeVirt by default. Dev and test environments are the natural place to start, because they have lower SLAs and more tolerance for disruption. Building them fresh on KubeVirt frees up VMware capacity without touching production.

Third, look at production VMs one at a time, timed against your renewals. For each one, the question is whether rebuilding it on KubeVirt costs less than keeping it on vSphere for another term. Some will be obvious. Some will stay put.

In the conversations we’ve had, teams worry about the technical side and lose their time on the people side. Planning for that gap is what keeps this from stalling.

When should we wait?

Not every organization should act right now. If you are mid-cycle on a VMware contract and the renewal is two years out, rushing to dodge a future increase can cost more than the increase. The organizations making the best calls treat this as a commercial problem to solve and avoid reacting to it like a crisis.

Start with three numbers:

  • The date of your next VMware renewal.

  • What an increase anywhere in that range would cost you per year.

  • How long it would take to build fresh on KubeVirt the VMs you would most like to stop paying for.

That math tells you whether the urgency is real or manufactured. For most organizations running production VMs on VMware right now, it says to start building new VMs somewhere else before the next renewal, because waiting makes the options worse and the pressure higher.

The VMs on Orion page covers how Orion manages vSphere, Proxmox and KubeVirt VMs together. If you want to see it over your own hosts, book a demo.

WRITTEN BY

Tony Como

Tony runs go-to-market at Juno, from first outreach to production deployment. He works across sales, partnerships, and operations to help technical teams move faster without adding infrastructure overhead.