Perhaps the Proxmox team could consider building its own version of virtio drivers with its own installer, signed by Proxmox. This would allow for faster patch deployment, as is done for other subsystems (ZFS, etc.).
@fweber
And one can still use the no-subscription repository to get updates: https://pdm.proxmox.com/docs/installation.html#proxmox-datacenter-manager-no-subscription-repository
I wouldn't do this in a corporate envionment though ;)
Just want to add the following, in order to make absolutely sure:
I have no problem with Chinese people or anyone speaking chinese. If you think that, then you are completely missing the point.
What I have a problem with is people who think...
But such storage hardware also has it's costs. If you need to invest in storage hardware you could also invest in enough hardware to use Ceph, at least if you plan with three compute nodes or more. The story might be different if you happen to...
I doubt that somebody that ask questions like the OP has the needed knowledge and experience to do this. So this ill-advised proposal is not helpful at all if not outright dangerous. YMMV
I think the best solution for you is this (assuming you don't have mission-critical applications...): 2 PVE nodes with ZFS replication + QDevice
Of course, you'll need to consider ZFS's asynchronous replication, but if you manage replication...
In your case, the best solution to cut the costs while keeping the system easy to manage is the solution B:
2 PVE nodes with ZFS replication + QDevice
Notes:
There are many tutorials for this setup on the web.
You can run the...
1 - Back up with Veeam Backup & Replication Community Edition
2 - Still using Veeam B&R: restore to ProxMox
3 - Optimize the new VM's settings in ProxMox (install and configure VirtIO drivers, optimize sockets and CPU cores, etc.)
That's it...