The usual use of the zero-day term is for vulnerabilities that are being exploited while there is no fix yet (for a supported/current version). That is something the administrator cannot do much about. This vulnerability is probably already fixed...
In any case, I don't think this is a 0day vulnerability, because on this is happen due to out date servers and bad servers administration, to say the least.
Many of this vulnerabilities are well-know documented, such as kernel and ssh...
Search for 8. in these posts here: https://forum.proxmox.com/threads/proxmox-virtual-environment-security-advisories.149331/ . PVE 8 is also vulnerable to lots of things unless completely up to date but it most likely does not get any updates...
So, you are:
Running a OS that is EOL since two years
Exposing it to the internet
Disabling the firewall
If this is not a troll, I hope the lesson was learned...
Perhaps you sould take a look in PVE-Zsync.
One doesn't need to have the node in cluster, I guess.
https://pve.proxmox.com/wiki/PVE-zsync
Just an idea.
Thanks for your feedback. FWIW, Ubuntu VMs run fine on our 144-core NVIDIA Grace system, but yeah, that's an ARMv9. We still can improve compat if it's cheap to do, or maybe just some config options needs changing. Can you please open a new...
Just got it loaded up on my Ampere Altra Max 128-core system, and install was a breeze.
Once I had it running, I tried creating an Ubuntu 24.04.1 arm64 server VM, and the process was going through fine... but at a certain point when the Ubuntu...
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only.
Proxmox VE 9.2 for arm64...
Starwind has a nice tools as well...
https://www.starwindsoftware.com/starwind-v2v-converter
I never used, but got friends that did it...
I rather use clonezilla or redorescue as I pointed out... Redorescue always work for me...
But, go ahead...
Please be aware that cache=writeback may lead to data loss in case of a power failure. It also works if you set cache=none and aio=native, but I ran into issues (BTRFS metadata corruptions) within VMs. Currently, I am using cache=none and...