Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> ... being able to do software patches of the underlying system without service outages is really desirable.

Yeah, that's what I was looking at Proxmox (8.x) for recently as well, but it never made it through basic qualification testing. VM migration's would randomly hang forever about 25% of the time. Definitely not a case of bad network interconnect either. :(

I'm using Ryzen 5000 series cpus on all the test gear though, and recently saw a mention that it may have been a known problem that's fixed. But not super keen on wasting more time.

What sort of cpus are your hosts using, and are you using your VMs with Ceph as their storage? :)



Great question! I haven't gotten that far yet. I have Proxmox running on a 12th gen i5 currently, and my other two compute nodes, a 3rd gen i7 laptop and a 7th gen i5, are currently still serving production workloads, so I haven't had a chance to set up a cluster yet. That said, I don't mind limiting features to lowest common denominator for the k3s control plane node, as I don't need gobs of power for it or advanced CPU features, and I imagine that's the pain you might be facing (though I'm new to Proxmox, so who can say?)

That said, I do have a NAS that I can provide both NFS and iSCSI storage to, so I imagine if I run NFS as the backing storage, I shouldn't have to worry about clustered file systems. Each compute does have local storage, but the plan is to provide that via a CSI for workloads that don't need to be highly available or where fault tolerance isn't a concern.


As a data point, the vm migration hangs aren't happening in testing any more. Looks like there really was a fix added to Proxmox recently.

Can proceed with more testing now. :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: