Proxmox Virtual Environment 9.1 Available
Postedabout 2 months agoActiveabout 2 months ago
proxmox.comTechstory
calmpositive
Debate
0/100
ProxmoxVirtualizationOpen-Source
Key topics
Proxmox
Virtualization
Open-Source
Proxmox Virtual Environment 9.1 is now available, marking a new release of the popular open-source virtualization platform.
Snapshot generated from the HN discussion
Discussion Activity
Active discussionFirst comment
22m
Peak period
19
1-2h
Avg / period
7.1
Comment distribution57 data points
Loading chart...
Based on 57 loaded comments
Key moments
- 01Story posted
Nov 19, 2025 at 9:35 AM EST
about 2 months ago
Step 01 - 02First comment
Nov 19, 2025 at 9:57 AM EST
22m after posting
Step 02 - 03Peak activity
19 comments in 1-2h
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 19, 2025 at 5:50 PM EST
about 2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45980005Type: storyLast synced: 11/22/2025, 12:04:07 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
(Perhaps if you're a Microsoft shop you're looking at Hyper-V?)
My personal dark horse favorite right now is HPE VM Essentials. HPE has a terrible track record of being awesome at enterprise software, but their support org is solid and the solution checks a heck of a lot of boxes, including broad support for non-HPE servers, storage, and networking. Solution is priced to move and I expect HPE smells blood in these waters, they're clearly dumping a lot of development resources into the product in this past year.
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.
You can grow out of either by just moving to self hosted, or you can avoid both for the virtualization part if you don't care about the VMware like GUI if you are an automation focused company.
If we could do it 20 years ago once VT-x for production Oracle EBS instances for a smaller but publicly traded company with a IT team of 4, almost any midmarket enterprise could do it today, especially with modern tools.
It is culture and web-ui requirements and FUD that cause issues, not the underlying products that are stable today, but hidden from view.
> KKR & Co. Inc., also known as Kohlberg Kravis Roberts & Co., is an American global private equity and investment company.
* https://en.wikipedia.org/wiki/KKR_%26_Co.
You can have a public company that invests in private companies, as opposed to investing in publicly listed companies (like $BRK/Buffett does (in addition to PE stuff)).
Sorry, but I bought Proxmox 7, but it is not comparable. Incus does everything (and more) with better interface, WAY better reliability, and also not like a hundred EUR or whatever. (100 EUR is fine with me if better, but not if not better...)
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.
Nothing is stopping you from doing this with Proxmox, right?
The demo does take ~10m to get into a working instance.
Proxmox has nice web GUI
[1]: https://blog.simos.info/how-to-install-and-setup-the-incus-w...
When it matures I’ll look into switching from Proxmox.
Cool part is I needed a more powerful Linux shell than my regular servers (NUCs, etc.) for a one off project, so I spun up a VM on it and instantly had more than enough compute.
I thought it might need gpu virtualization?
do you do it with passthrough?
Another benefit is block-level backups of the VMs (either with qcow2 disks files or ZFS block storage, which both support snapshots and easy incremental backups of changed block data only)
Proxmox is great for this, although maybe not on a laptop unless you're ready to do a lot of tweaks for sleep, etc.
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.
https://youtu.be/4-u4x9L6k1s?t=21
>no mature orchestration
Seems to borrow the LXC tooling...which has a decent command line tool at least. You could in theory automate against that.
Presumably it'll mature
Then the opportunity to get rich by offering an open source product combined with closed source extras+support was invented. I don't like this new world.
Edit: Somewhere along the line, we also lost the concept of having a sysadmin/developer person working at like a municipality contributring like 20% of their time towards maintenance of such projects. Invaluable when keeping things running.
Remember: Not all commercial users are FAANG rich. Counties/local municipalities count as commercial users, as an example.
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.
And how does Ceph/RBD work over Fibre Channel SANs? (Speaking as someone who is running Proxmox-Ceph (and at another gig did OpenStack-Ceph).)
There exist many OCI runtimes, and our container toolkit already provides a (ball parked) 90% feature overlap with them. Maintaining two stacks here is just needless extra work and asking for extra pain for us devs and our users, so no, thanks.
That said, PVE is not OCI runtime compatible yet, that's why this is marked as tech preview, but it can be still useful for many that control their OCI images themselves or have an existing automation stack that can drive the current implementation. That said, we plan to work more on this in the future, but for the midterm it will be not that interesting for those that want a very simple hand-off approach (let's call it "casual hobby homelabber"), or want to replace some more complex stack with it; but I think we'll get there.
Adventures in upgrading Proxmox - https://news.ycombinator.com/item?id=45981666 - Nov 2025 (10 comments)
I learned stuff like this years ago with upgrades to debian/ubuntu/etc - upgrading a distribution is a mess, and I've learned not to trust it.
22 more comments available on Hacker News