31–40 of 80 posts
"Proxmox VE is using a newer Linux kernel 6.14.8-2 as stable default enhancing hardware compatibility and performance." kernel.org don't even list version 6.14 anymore. do they backport security patches on there own?
I like Promox a lot, but I wish it had an equivalent to VMware's VMFS. The last time I tried, there wasn't a way to use shared storage (i.e., iscsi block devices) across multiple nodes and have a failover of VMs that use that storage. And by failover I mean moving a VM to another host and booting it there, not even keeping the VM running.
Proxmox has built-in support for CEPH, which is promoted as VMFS equivalent. I don't have much experience with them, so can't tell if it's really on the same level.
One advantage Ceph has over VMware is that you don't need specially approved hardware to run it. Just use any old disks/SSDs/controllers. No special extra expensive vSAN hardware.
But I cannot give you a full comparison, because I don't know all of VMware that well.
I have only recently moved to proxmox as the Hyper-V licensing became too opressive for hobby/one-person projects use. Can someone tell me wether proxmox upgrades are usually smooth sailing, or should I prepare for this being an endeavour?
I like Promox a lot, but I wish it had an equivalent to VMware's VMFS. The last time I tried, there wasn't a way to use shared storage (i.e., iscsi block devices) across multiple nodes and have a failover of VMs that use that storage. And by failover I mean moving a VM to another host and booting it there, not even keeping the VM running.
Use any of these with the built in HA manager in proxmox
We are really happy with proxmox for our 4 machine cluster in the group. We evaluated many things, they were either to light or to heavy for our users and/or our group of hobbyist admins. A while back we also set up a backup server. Forum is also a great resource. I just failed to contribute a pull request via their git email workflow and I am now stuck with a non-upstreamed patch to the LDAP Sync (btw. the code ther…
"Proxmox VE is using a newer Linux kernel 6.14.8-2 as stable default enhancing hardware compatibility and performance." kernel.org don't even list version 6.14 anymore. do they backport security patches on there own?
I don't know what they are currently doing, but historically Proxmox uses Debian as the OS base but with Ubuntu as the kernel source. So they rely on the Ubuntu security team backporting security patches for the kernel.
I have only recently moved to proxmox as the Hyper-V licensing became too opressive for hobby/one-person projects use. Can someone tell me wether proxmox upgrades are usually smooth sailing, or should I prepare for this being an endeavour?
Never had a problem with them. Just put each node in maintenance, migrate the VMs to another node, update, move the VMs back. Repeat until all nodes are updated.
I've heard good things about XCP-ng [1] as well: anyone use both that can lay out the pros/cons of each? [1] https://en.wikipedia.org/wiki/XCP-ng
"Proxmox VE is using a newer Linux kernel 6.14.8-2 as stable default enhancing hardware compatibility and performance." kernel.org don't even list version 6.14 anymore. do they backport security patches on there own?
(Ignore this if it’s irrelevant and I’m missing the point, which is always a distinct possibility)
> Many Linux distributions provide their own "longterm maintenance" kernels that may or may not be based on those maintained by kernel developers. These kernel releases are not hosted at kernel.org and kernel developers can provide no support for them.
> It is easy to tell if you are running a distribution kernel. Unless you downloaded, compiled and installed your own version of kernel from kernel.org, you are running a distribution kernel. To find out the version of your kernel, run uname -r: