When I came on board we were using ganeti for dev/stg and VMWare for production. But the difficulty of monitoring VMWare (we were moving away from SAN to local storage, and doing a RAID array monitor was a PITA) and administering (via Windows GUI, which I had to run via a VM on my Linux workstations), plus the licensing weirdness (clusters of size 5 were a sweet spot, any more shifted the price dramatically).
So I eventually shifted our production to ganeti as well, because it had been so solid in dev/stg. It's all manageable from the Linux CLI, and it works really, really well. It's basically a management layer on top of kvm+qemu+drbd+ceph. https://ganeti.org/
The other popular option, which I ran in my previous work, is Proxmox. It is probably a more comfortable analog to VMWare users. https://www.proxmox.com/en/proxmox-virtual-environment/overv...
I assume you're referring to the (ancient) VIC? Vsphere has been all web based for a long long time now. It had probably just never been upgraded.
Also I'm curious why the move to local storage, what do you do if a host dies?
What we did if a machine failed was: design our apps to be resilient. Basically everything we run can survive machine failures via either app design or corosync/pacemaker.
We're a pretty small shop, but we ran an experiment of trying a SAN (an HP of some sort) and every year like clockwork the redundant SAN would fall over and take our whole stack with it. Every year like clockwork HP would say "you aren't running the latest firmware, try this one". Equallogic at another job was super reliable but also was easily twice the price of the HP.
The simplicity and redundancy of local storage has largely been a huge win. We did have a couple of Dell machines where the drive arrays seemed to fall over, possibly because of too much IO, but Dell identified a particular SSD and the array has been solid for 3-4 years since then.
Desktop? Learn to live with Oracle's VirtualBox and pray you never ever get audited for the guest toolkit acceleration.
Small home lab? Hand-roll QEMU-KVM.
Worth mentioning that the Extension Pack is distributed separately[1] from VirtualBox itself and requires deliberate installation. Put more simply, it's an opt-in.
I'll also mention that, at least for most personal and even small business use cases, you probably don't need the features provided by the Extension Pack[2]:
* VirtualBox Remote Desktop Protocol (VRDP) support.
* Host webcam passthrough.
* Intel PXE boot ROM.
* Disk image encryption with AES algorithm.
* Cloud integration features.
[1]: https://www.virtualbox.org/wiki/Downloads
[2]: https://www.virtualbox.org/manual/ch01.html#intro-installing
[1] https://www.parallels.com/products/ras/remote-application-se...
[2] https://www.parallels.com/products/psw/
[3] https://www.nutanix.com/uk/products/nutanix-cloud-infrastruc...
You might find that some workloads are best fit for a modern orchestrator running containers such as Kubernetes or Nomad, or a SaaS, or a PaaS/IaaS, or a different hypervisor such as Proxmox or full infrastructure management platform such as OpenStack.