I’ve quietly built a proxmox cluster in our environment for semi-prod workloads for when the inevitable windows host has issues.
I’ve quietly built a proxmox cluster in our environment for semi-prod workloads for when the inevitable windows host has issues.
There are a few broad categories to building one of these platforms.. core virtualization ("relatively easy"), device model ("medium hard"), storage management ("hard"), management plane ("medium hard").
VMWare popularized x86 core virtualization and defined their own device model because they were the early market leader. But the device model is pretty bizarre and I haven't been particularly impressed by the guest driver quality over the years. VMFS and vSAN seem good for storage, the latter being better than anything open source. Management plane was mediocre, I remember it took a while to move off Flash and fat clients while cloud vendors were showing none of that was necessary from inception, and everything is kind of in a walled garden by design (embedded DB etc).
VSAN was a weird one until I understood the logic behind it, but the licensing costs kind of brought on-par to buying a SAN and be happy.
I haven't touched Microsoft Hyper-V.
I don't think anyone finds this flavor of activity beneficial. What's beneficial is the underlying system that is sufficiently free and flexible that great things (like VMware to begin with) are possible. As much as we don't like "this" we don't want to put any bureaucrats in power to squash creativity and enterprise.
Much like freedom of speech means someone can speak abhorrently, freedom of enterprise means someone can do bad or dumb business things. But we enjoy the thing in totality.
Ultimately, the purpose of a system is what it does.
We've structured our society such that performing this type of activity is extremely lucrative, and financial engineering is by all appearances the endeavor that humans value above all others.
That was literally Broadcom’s reason for existing before Avago even acquired them. It’s the other half of the Qualcomm/Broadcom telecom duopoly.
No?
I do understand the argument that it can be considered as a benefit for society if companies that have a very incompetent management that falls for this kind of trap of getting locked in by some vendor without having an emergency escape plan available get milked or even get bust. :-)
Problem with incentives, I would say.
Microsoft hides their best stuff in SCVMM, which is another product and another license they want you to purchase. Anytime I've asked someone from MS why I can't X like I can in vCenter the response was usually, "oh, it's in System Center. FCM, HVM are just stripped down. If you need it you should buy System Center."
But, hey, The Reg says that VMware is now claiming that vSphere Standard was never really cancelled.
https://www.theregister.com/virtualization/2026/09/02/vmware...
I don't think SCVMM is as bad as you portrait. I've used both SCVMM and vCenter. vCenter is so far ahead. And SCVMM was getting there until 2022. When they stopped trying.
If you think about it, all hyperscalers are hardly any different from old timesharing OSes, the only big difference is the way we get to log into the platform.
I assume this means that you were using Vmware Workstation? The VDDK is for Vmware vSphere, which -IIRC- runs on Linux and coordinates computers running ESXi, which are where vSphere VMs actually run.
Not that many people are going to be using Vmware Workstation to run a large number of VMs.
And I was like... what virtual host?
What I found was Server 2003 running on VMWare Workstation, running on a Windows 7 Dell PC sitting at the bottom of a rack.
A lot of people think VMWare Workstation is the pinnacle product of the company and I have NFI how this came to be.
Sure, a type-1 hypervisor like vSphere is technically better since there's no host OS creating unmanageable contention and if you have guests with higher performance requirements then yeah it's settling for something half-assed.
But in reality, we have some similar shit to a "fax server" that has manually set up weird manufacturer printer settings (local admins tried to be automated/distributed) and old third-party software libraries that "infects" a system globally (2 versions of that library cannot co-exist on a computer).
If that piece of crap can be contained on a VM, as long as it's contained and keeps trucking after a restart/powercycle everyone is happy. What kind of VM container hosts it is really secondary.
(What the software in question is can probably be inferred from the comment, the software is liked by users at the client so it's not going away)
I disagree. protoculture's core statement seems to be:
A lot of people think VMWare Workstation is the pinnacle product of the company and I have NFI how this came to be.
A company's pinnacle product can be completely useless to me, but that doesn't change the fact that the products of theirs that I do use are very simple and unimpressive when compared to it. [0]Having said that, I expect that a lot of people think Vmware Workstation is Vmware's pinnacle product because they've never heard of vSphere, ESXi, or anything else the company has made. "People have no knowledge of like 95% of what most companies do." is always a solid first guess when trying to work out confusion like protoculture's.
[0] Please spare me the "But how can it be a pinnacle product if it's not useful to you?" retort and ones like it. I've deliberately made a distinction between a product's usefulness to me personally and the sophistication of that product.
If I were starting a company today I would make sure that the majority of my apps were web based. (CRM[netsuite or sf.com], O365/GoogleDocs, workday|gusto, etc.)
First, someone has to pay to migrate apps, and as often as not the resources to do that aren't available. Sometimes you do the math and it doesn't make finacial sense to allocate those resources. And sometimes you just can't move apps. The vendor might not support vm/cloud/web deployment. Or, very common in manufacturing, you have an app that runs a machine and requires a very, very specific hw/sw environment to be supported.
Next, there's that whole regulated thing. We spend a lot of time in front of federal/national regulators explaining how we do things so that we don't screw up your mortgage or whatever. And those regulators take careful notes. So if I've spent the last 10 years explaining how we have this amazing VMWare deployment that ticks all the boxes, they're going to want some very, very detailed explanations of how HP VME or Proxmox or whatever is going to tick all the same boxes at least as good as VMWare did. And we're inviting a lot of scrutiny for a couple of years to make sure we did it right. It's a lot of work.
Sometimes you weigh everything, not just 'it costs less' or 'Broadcom are a bunch of assholes' or 'we don't want bros on HN to think we're suckers', and the answer is legitimately "the divorce isn't worth it".
Many businesses might do better pushing everything to web apps, but SaaS introduces a whole bunch of other issues in highly regulated worlds like finance. It's not always the right answer.
Why is your place of work not moving wholesale to Proxmox? It's mad that HyperV is chosen as a solution in this day and age.
If they build their new Datacenter Manager offering into what vCenter offered and abstract away all the ugliness (imagine creating a "distributed" switch on Proxmox with two clicks) I think they will make a killing.
24/7 support will be available starting in October:
* https://www.proxmox.com/en/about/company-details/press-relea...
The other thing perhaps worth noting that the entire stack is open source, even Proxmox's 'special sauce' for management. Depending on your organization, if you can solve a problem with Debian (and Qemu) you can solve a problem with Proxmox.
Better to just use same automation you use for VMs to just keep fleet of bare Debian + KVM machines.
Proxmox is for when you don't have a bunch of Linux experts on board. And that's also kinda what enterprises want to pay for, removing "liability" of having to keep very competent team.
...the fact that ends up costing them more everywhere is of no concern to middle management
Proxmox gives you centralized management of a fleet of clustered systems with a very handy GUI (as well as CLI and API) that's used by many thousands of installations, which is a lot better than try to cobble together something yourself IMHO. Just because you have "a bunch of Linux experts on board" doesn't mean they have to 'waste' their time on re-inventing the wheel for management of VMs.
At my last job we had plenty of Linux folks and primarily ran a whole bunch of OpenStack, but we still used Proxmox for standalone management of VMs for 'tier zero' services (e.g., DNS, SMTP, LDAP, NTP) of various sorts that OpenStack itself depended on.