by generalizations
3 subcomments
- > As an aside... Because one node didn't start, and my Proxmox cluster has only two nodes, it can't reach quorum, meaning I can't really make any changes to my other node, and I can't start any containers that are stopped.
I've recently added another Zigbee dongle, that supports Thread, and it happens to share same VID:PID combo as the old dongle, so due to how these were mapped into guest OS, all my light switches stopped working. I had to fix the issue fast.
Lesson in here somewhere. Something about about a toaster representing the local intelligence maxima?
- Just adding my anecdata. I started using ESXi around 2016 for homelab purposes. This paid off nicely as my $CORP also uses VMWare products, so it was easy and natural to get into VMs and fix them up as needed.
Pretty unhappy about the Broadcom acquisition as VMWare previously seemed to care about the homelab market and recognized the value created by letting hobby admins learn their tools. That's going away now and Broadcom hopes the locked in market will provide enough income to suit their short term goals.
Anyway, I switched to Proxmox 9 in my lab this year and couldn't be happier. It's so much more powerful, flexible, and intuitive after one spends a few days in the UI. I ported all my VMs over and things are rock solid and better than ever under Proxmox.
My local systems team at $CORP knows of Proxmox but acknowledges nothing will be changing soon with our environment. But time will tell I suppose.
- Related ongoing thread:
Proxmox virtual environment 9.1 available - https://news.ycombinator.com/item?id=45980005 - Nov 2025 (56 comments)
- Man Proxmox... I love it, I use it, but I swear there has to be a more straightforward way to implement this technology.
by danishSuri1994
3 subcomments
- It seems like a lot of the pain comes from the fact that hardware passthrough behaves so differently under LXC vs VMs.
Has anyone here found a stable way to handle USB / PCIe device identity changes across updates or reboots?
That part always feels like the weak point in otherwise solid Proxmox setups
by evanjrowley
0 subcomment
- I ran into the same issue over the weekend. The end-goal for my Proxmox setup is basically the same deployment you have. It's good to see the issue was addressed quickly by the community.
by thesurlydev
3 subcomments
- I recently gave up on Proxmox for my home lab needs after a failed upgrade from 8 to 9. I also never liked the feeling of not having an easy to use API.
- Btw the issue that the author encountered are not really with proxmox itself but with an out-of-tree kernel driver they installed.
Any debian system (proxmox is based on debian) would have broken in a similar (if not the exact same) way.
- > Running docker inside LXC is weird.
Knowing when to use a vm and when to use a container is sometimes an opaque problem.
This is one of those cases where a VM is a much better choice.
- Look ma, I'm on the TV.
The merch is in the back, sub to the YouTube channel...
by throw0101c
0 subcomment
- See also "Upgrade from 8 to 9":
* https://pve.proxmox.com/wiki/Upgrade_from_8_to_9
And "Known Issues & Breaking Changes (9.1)":
* https://pve.proxmox.com/wiki/Roadmap#9.1-known-issues
by john-carter
0 subcomment
- [flagged]
by Jeff-Collins
1 subcomments
- [flagged]
Hacker News