It's all based around open source projects virt-v2v and Migration Toolkit for Virt, and the typical target is OpenShift Virtualization.
There are various zero-copy options if you're using specific storage. In the best case the downtime for each guest can be as little as a few minutes. If the storage stars don't align then it can take a few hours per VM (but conversions happen in parallel, dozens or hundreds at a time).
[I don't have any specific knowledge about where this Tesco account is going. We have plenty of competitors. Everyone is dining at the Broadcom trough right now. Broadcom's "strategy" is absolutely baffling to me.]
Edit: Almost forgot that I gave a 5 minute lightning talk about it: https://pretalx.com/devconf-cz-2024/talk/SN93LG/
I know plenty of Enterprise customers who cannot move easily and just renewed 3 year VMware licenses for their cluster at insane rates. They are planning on moving but I'd be shocked if they complete it. $LastCompany had VMware footprint I know will be very difficult to move off, deployments, monitoring, backups were all dependent on VMware. There are plenty of US Government entities who are not even considering it at this time.
Also, Broadcom has slashed expenses so I wouldn't be shocked if profit margins are crazy. This article: https://www.theregister.com/software/2025/03/07/bulk-of-big-... indicates over 1 Billion additional revenue per quarter
If you look deeper into the migration article, it's pointed out that they are already facing migration challenges. I wouldn't be shocked if 3 years later, there are some workloads still running on VMware, you can't easily get them off and just renews insane licensing cost for much smaller hardware footprint.
What about the long term? Who care, massive money made and they can use that to keep going.
The future is Snickers!
I understand that this is normal but I've never understood it.
If all the containers are running the same company's applications (so they don't care about security boundaries between them), what's the difference between having all the containers under the same kernel vs separate kernels?
Note: if you want to conflate “containers“ with an entire job management and scheduling system (“k8s”) then you’re not actually talking about the current target customer for VMware.
None of those matter in the slightest with containers. Why would you need to reallocate hardware resources when the containers can run on another piece of hardware? You would snapshot the relevant storage, not the whole OS and kitchen sink.
VMs as an intermediary between hardware and containers is just a waste of resources - both directly (RAM, CPU, storage to run a useless OS with no benefit) and indirectly (all of those VM's OS needs maintaining and patching).
It's basically a hold over from the olden days of "everything is a VM".
Sure, most of what we do is very cattle and we could run on bare hardware but why not take advantage of easy to add flexibility.
Your "machine for testing" would be a container. Decommissioning a container is easy. Decommissioning a physical machine only happens when it's obsolete.
It’s not growing in any meaningful way relative to other technology businesses.
(As an end-user sort of person, I get a strong smell of Bladerunner from this kind of thing, where you can see old PCs in the background on top of decks with cables running out of them).
Usually the story is they're running something like CNC control which originally ran on baremetal, then got virtualized onto VMware when the hardware died (possibly using VDI to make it appear on a terminal close to the machien), and it's still doing the same thing effectively today.
And number of those has nowhere to go but down too. There is no growth in either of those, because everyone who will at some point try to get rid of them. Not all, not immediately, but the ultimate trajectory is down.
Also known as incompetence. Broadcom's business model is public. Their plans for VMware were public from when the acquisition was announced.
Those companies had years to plan how to get rid of everything VMware. Instead they paid through the nose to postpone the inevitable for a few years.
If one believes that they intend to get new VMware customers, or that they intend to have more than single-digit numbers of customers on VMware ten years from now, I can see how that might make their strategy baffling.
They appear to have made a lot of money doing what they're doing, so it looks to be working quite well for them... regardless of what the public or their former customers think about it.
Lots of orgs have been documenting their moves to KubeVirt over the past year or so. There's KubeCon video recordings on the youtube channel from Amsterdam with lots of this kind of stuff, especially from european end users.
One thing I find consistent is orgs are also looking at the whole stack, this is just another major component of digital sovereignty.
Disclaimer: work for CNCF on this but worked on the first version of VMWare Tanzu so every announcement in this space is interesting lol.