Comment by antithesis-nl

Comment by antithesis-nl 3 days ago

32 replies

Well, the Enterprise-hypervisor market is certainly wide open right now, due to Broadcom turning the financial screws on VMware customers hard. There are, broadly, two categories of potentially-profitable VMware customers up for grabs:

-Large enterprises that previously purchased hardware-with-accompanying-VMware-licenses from OEMs like Dell-EMC: Broadcom refused to even honor pre-acquisition license keys from these sources, leaving many private data centers in the lurch, unless they paid a huge premium for a new Broadcom-originated annual subscription (whereas the original key was one-off)

-Service providers with an ongoing "small-percentage-of revenue per year, payable in arrears" agreement, that were suddenly forced into a "hard vCPU and vRAM limit" subscription, payable for at least 2 years upfront.

However, the magic word for both customer segments is "vMotion", i.e. live-migration of VMs across disparate storage. No OSS and/or commercial (including Hyper-V) solution is able to truly match what VMware could (and can, at the right price) do in that space...

lenerdenator 3 days ago

> However, the magic word for both customer segments is "vMotion", i.e. live-migration of VMs across disparate storage. No OSS and/or commercial (including Hyper-V) solution is able to truly match what VMware could (and can, at the right price) do in that space...

Someone's gonna start working on that soon. Necessity is the mother of invention.

To me, this will be the UNIX wars moment for virtualization.

Originally, UNIX was something AT&T/Bell Labs mainly used for their own purposes. Then people wanted to use it for themselves. AT&T cooked up some insane price (like $20k in 1980s money) for the license for System V. That competed with the BSDs for a while. Then, some nerd in a college office in Finland contributed his kernel to the GNU project. The rest is history.

UNIX itself is somewhat of a niche today, with the vast majority of former use cases absorbed by GNU/Linux.

This feels like an effort by Broadcom to suck up all of the money in the VMWare customer base, thinking it's too much of a pain in the ass to migrate off of their wares. In some circumstances, they're not wrong, but there's going to be teams at companies talking about how to show VMWare the door permanently as a result of this.

Whether Broadcom is right that they can turn a profit on the acquisition with the remaining install base remains to be seen.

  • azurelake 2 days ago

    You have to understand that Broadcom isn't actually Broadcom the chipmaker. It's a private equity firm that used be named Avago Technologies before it bought Broadcom. So squeezing until there's nothing left is the plan.

    https://digitstodollars.com/2022/06/15/what-has-broadcom-bec...

    • lenerdenator a day ago

      > The truth is Broadcom is not a semiconductor company. Nor is it a software company. It is a private equity fund, maximizing cash flow from an endless series of acquisitions. This is disheartening to many in the semis industry and probably confusing to those in software.

      I hate when finance people talk like this.

      No, it's not confusing to people in software. We're well aware of your (finance) industry's reputation of sucking capital out of necessary, competitive companies for your own personal gain. If we thought we could get away with it, we'd do something about it.

  • pjmlp 2 days ago

    I consider UNIX/POSIX becoming niche, including GNU/Linux, for the so called cloud native workloads.

    The large majority of managed languages being used in such scenarios, compiled to native or VM based, have rich ecosystems that abstract the underlying platform.

    Moreso, if going deep into serverless, chiseled containers, unikernel style, or similar technologies.

    Naturally there is still plenty of room for traditional UNIX style workloads.

noja 3 days ago

What can VMware do in this vmotion space?

The docs says open source can do a live migration, see https://www.linux-kvm.org/page/Migration and https://docs.redhat.com/en/documentation/red_hat_enterprise_...

  • b5n 2 days ago

    The majority of vmware customers could get by with qemu/kvm + pacemaker/corosync, but that requires hiring people who can read a manpage.

  • mjevans 2 days ago

    Vaguely like MS Active Directory vs Kerberos. The really big thing 'vmotion' provides is 'things just work' vs flexibility of options but more effort required.

tart-lemonade 3 days ago

Third is academia. Even with a marginal academic discount, it doesn't come close to offsetting the price hikes. When the choice is between slashing personnel budget and minimizing the usage of/completely migrating away from VMware before the next renewal, there's really no choice in the matter, especially with the difficulty of firing employees.

kazen44 2 days ago

Another magic word that Vmware has which no other vendor does the same is NSX. (network virtualization).

proxmox is lightyears behind this usecase, and so are most other vendors. Especially if you are building private/public clouds with multi tenancy in mind.

NSX is really well designed and scales nicely, (it even has MPLS/EVPN support for Telecom Service Provider integration).

Most open source and other commercial offerings have solved both the compute and storage aspect quite well. But on the networking front, they a really not comparable.

Proxmox for instance, only supports a vxlan encapsulation or vlans, without support for a proper control plane like EVPN. Heck, route injection by BGP is only doable by DIY'ing it ontop of proxmox.

"just using vlans" is not going to cut if you want to really scale across datacenters and with multiple tenants. NSX does this all really nicely without having to touch the network itself at all thanks to encapsulation and EVPN route discovery.

SteveNuts 3 days ago

Hashicorp has some Nomad drivers for Qemu and a beta version that uses libvirt. However it's fairly immature and lacks a lot of features they would need to be competitive there.

Since IBM already has OpenShift I'm not sure how much time and effort they want to put into Nomad virtualization, but I'd love it as an alternative to Kubernetes.

trebligdivad 3 days ago

libvirt+qemu can do live migration across disparate storage; I know quite a lot of people want to use it. I'm curious in which ways you find the vMotion stuff does well with that.

mvdwoord 2 days ago

I would think another issue for a lot of existing large VMware customers is NSX (incl. dynamic firewalling), orchestration (vRA/vRO), vROPS, and the gazillion integrations that have been built with tight coupling at both ends. Swapping that out is not an easy task, and the "digital transformations" some of the available products are banking on take a lot of time in real life.

oneplane 2 days ago

Xen (and XenServer and XCP and the Citrix banded stuff) have been able to live migrate VMs for a really long time. Definitely not something special to VMWare.

Realistically, all the legacy workloads (those that are singletons and can't be load-balanced, need an active GUI session etc) are going to to be problems forever, even if you keep VMWare around.

UltraSane 2 days ago

" Broadcom refused to even honor pre-acquisition license keys from these sources, leaving many private data centers in the lurch"

How is this not contract violation?

gerdesj 2 days ago

>However, the magic word for both customer segments is "vMotion", ... . No OSS and/or commercial (including Hyper-V) solution is able to truly match what VMware could (and can, at the right price) do in that space...

Storage vMotion requires a hefty license (as does DVS and the other useful things, such as containers). Proxmox does it all out of the box at a very reasonable price point.

Hell, VMware wont even let you use LLDP until your pissing money out of all orifices. You get CDP only for "free".

After 20+ years of being a VMware fanboi I am migrating all my customers to Proxmox. I've had enough.

  • zozbot234 2 days ago

    > Proxmox does it all out of the box at a very reasonable price point.

    Live migration of containers via the CRIU featureset (checkpoint+restore in userspace, which is now part of the mainline Linux kernel) is also an interesting theoretical possibility - AIUI the Kubernetes folks are at least thinking about supporting it. (Live migration fits remarkably well with containers since it requires comprehensive namespacing of all system resources - abstracting away from any dependence on the local machine - which is also how containerization works to begin with.)

    • worthless-trash 2 days ago

      If live migration is the key to vmotion, I think that this has been working for some time between like-cpu deployments.

zellyn 3 days ago

I think Oxide's stuff does live migration, but I don't know how well it runs on non-Oxide hardware.

  • antithesis-nl 3 days ago

    As far as I can tell, Oxide is all about compute, not storage -- i.e., as long as you can guarantee a stable storage layer, your Oxide racks will be fine.

    VMware used to go a bit further, in that they allowed your compute nodes to fail and/or your storage nodes to fail, without adverse effects.

    If Oxide can do that, out-of-the-box, right-now, they'll be having a field day. Otherwise, my reservations about Oxide's business model remain...

    • zellyn 3 days ago

      I _think_ their storage layer is fault tolerant. Not sure though. Hopefully one of them will weigh in here.

      • steveklabnik 2 days ago

        This is not my area of expertise, so I'll quote from our website: https://oxide.computer/product/storage

        The storage service uses OpenZFS for all data storage. This marries Oxide’s distributed data storage and multi-node failure resiliency with the dependability and efficiency OpenZFS has earned in its 20 years of running demanding workloads.

        The Oxide control plane monitors performance metrics as another early signal of component failure. As sleds and SSDs are rotated in and out, the Oxide control plane migrates storage regions to ensure the appropriate redundancy.

        OpenZFS checksums and scrubs all data for early failure detection. Virtual disks constantly validate the integrity of your data, correcting failures as soon as they are discovered.

  • houseofzeus 3 days ago

    I think most of these solutions including OpenShift Virtualization, Hyper-V, Proxmox, etc. do live migration. What the previous post is talking about is some of the more advanced VMware live migration features like storage live migration and cross-cluster live migration and some of the automations layered over the top of them.

wesapien 3 days ago

vMotion is about host failure. If a blade server dies, the vms can be spun up on another blade. Storage is same.

  • blown_gasket 3 days ago

    You're thinking of high-availability, which registers the vmx file of the VM to a physical server that isn't dead, then powers the VM back on. Whereas vMotion is either a cold or live-migration of the VM + memory state (if the VM is powered down, there is no memory state to migrate).

  • antithesis-nl 3 days ago

    > vMotion is about host failure

    No? It's also about load balancing and draining compute/storage resources in preparation for maintenance.

    Most pertinently: as long as your alternative doesn't cover any vMotion use-cases, customers will remain 'in talks' with Broadcom...

    • toredash 3 days ago

      Fun that people -still- don't understand the feature set that VMware provides.

      He/She is thinking about VMware Fault Tolerance