31–40 of 81 posts
The only thing missing making Proxmox difficult in traditional environment is a replacement for VMware's VMFS (cluster aware VM file system). Lots and lots of organizations already have SAN/storage fabric networks presenting block storage over the network which was heavily used for VMware environments. You could use NFS if your arrays support it, but MPIO block storage via iscsi is ubiquitous in my experience.
Proxmox (and XCP-ng?) seems to be "the" (?) popular alternative to VMware after Broadcom's private equity-fuel cash grab. (Perhaps if you're a Microsoft shop you're looking at Hyper-V?)
Proxmox (and XCP-ng?) seems to be "the" (?) popular alternative to VMware after Broadcom's private equity-fuel cash grab. (Perhaps if you're a Microsoft shop you're looking at Hyper-V?)
Proxmox (and XCP-ng?) seems to be "the" (?) popular alternative to VMware after Broadcom's private equity-fuel cash grab. (Perhaps if you're a Microsoft shop you're looking at Hyper-V?)
Proxmox (and XCP-ng?) seems to be "the" (?) popular alternative to VMware after Broadcom's private equity-fuel cash grab. (Perhaps if you're a Microsoft shop you're looking at Hyper-V?)
um broadcom is publicly traded as $AVGO...?
Earlier quoted context omitted.
Proxmox is free, too. Incus looks nice, though it looks to be more API driven , at least from the landing page. I can't attest to Proxmox in a production/cluster environment but (barring GPU passthrough) it's very accessible for homelab and small network.
GPU passthrough works fine? I use that for transcoding in Jellyfin.
Watching hypervisors slowly improve over the last few years has been amazing. They aren't quite to the point that I will install them under any new hardware I buy and then put my daily driver OS on top, but they are very close. I think a strong focus on creating 'the OS under your OS' experience seamless could open up a lot more here.
But the moment you stop trying to do everything locally Proxmox, as it is today, is a dream.
It's easy enough to spin up a VM, throw a clients docker/podman + other insanity onto it and have a running dev instance in minutes. It's easy enough to work remotely in your favorite IDE/dev env. DO I need to "try something wild", clone it... build a new one... back it up and restore if it doesn't work...
Do I need to emulate production at a more fine grained level than what docker can provide: easy enough to build something that looks like production on my proxmox box.
And when I'm done with all that work... my daily driver laptop and desktop remain free of cruft and clutter.
Earlier quoted context omitted.
What do you find wrong with "this new world"? For context, I'm using their free offering for my home server, for 6-7 years now. Happy as a clam.
It enables Oracle-like behavior. Once you're locked in as commercial user they can do whatever they want. Remember: Not all commercial users are FAANG rich. Counties/local municipalities count as commercial users, as an example.
In general, I don't think this is a threat. I think the problems begin with proprietary offerings, like they so often do in the cloud. Then's the time when vendor lock-in takes its toll. But even with AWS, if you stick to open interfaces, it's easy to leave.
Proxmox (and XCP-ng?) seems to be "the" (?) popular alternative to VMware after Broadcom's private equity-fuel cash grab. (Perhaps if you're a Microsoft shop you're looking at Hyper-V?)
Talking to midmarket and enterprise customers and nobody is taking Proxmox seriously quite yet, I think due to concerns around support availability and long term viability. Hyper-V and Azure Local come up a lot in these conversations if you run a lot of Windows (Healthcare in the US is nearly entirely Windows based). Have some folks kicking tires on OpenShift, which is a HEAVY lift and not much less expensive than mo…
This wasn't my experience in over a decade in the industry.
It's Windows dominant, but our environment was typically around a 70/30 split of Windows/Linux servers.
Cerner shops in particular are going to have a larger Linux footprint. Radiology, biomed, interface engines, and med records also tended to have quite a bit of nix infrastructure.
One thing that can be said is that containerization has basically zero penetration with any vendors in the space. Pretty much everyone is still doing a pets over cattle model in the industry.