Sending notifications for exceeding storage limits is not possible with the current PBS feature set, using external monitoring is the best way to achieve this [0].
FWIW there is some development work in adding protections for datastores running...
You could try needrestart: needrestart man page
By default, it runs in interactive mode, i.e. if you update from the CLI (apt update && apt full-upgrade), it tells you whether a reboot is necessary, lists all services that need to be restarted...
There is another old thread about that topic as well as bugzilla entry.
https://forum.proxmox.com/threads/feature-request-proxmox-ve-scheduled-tasks.152468/
https://bugzilla.proxmox.com/show_bug.cgi?id=7539
You could only grant them access to manually execute shutdowns via the UI with VM.PowerMgmt perms on a pool or on individual guests.
For the scheduling you'd need to go outside PVE. Either drive the API directly with a token scoped to that same...
Virtual machine support is better classified first by CPU architecture rather than by the guest OS itself. At this point, the relevant architectures are x86 and ARM.
The next question is whether the guest OS supports the virtual hardware...
PVE doesn't have a 'supported' list, I am assuming this is a list of VMs you're wanting to export from an existing system like vSphere?
You can run essentially any x86-64 OS, so all of those are fine. The OS Type field in PVE isn't a...
I swapped the nics and it made a huge difference, I know mellanox is better, but damn.
Ceph Network Swapping Test Summary
Workload TypeMetricBefore (Old Public/Cluster Setup)After (ConnectX-5 for Cluster Network)Performance Impact...
There is now a newer pve-manager with version 9.2.12 available on the pve-test repo and a backport of that as 8.4.22 for PVE 8's pvetest repo, matching our respective test repo of the ceph-squid and ceph-tentacle releases.
There is some better...
This can be done gradually, but needs a bit of care. We're currently in the process of finishing a migration helper tool and providing documentation for how to do this.
I am on the Ceph users email list, and it seems the fix is not a simple update, and will not be trivial. You have to use new authentication keys, aes256k, and rotate the keys used, and for that (for rbd storage at least), shutdown all VMs. And...
https://www.openwall.com/lists/oss-security/2026/08/19/4
https://www.openwall.com/lists/oss-security/2026/08/20/20
;tldr There are flaws in the currently used authentication mechanism for CephX. Versions 19.2.6 and 20.2.4 introduce new...
I disagree. For a non-technical user ( which OP clearly is ) a managed service ( be it oiffice365 or nextcloud/onlyoffice if you don't want to depend on Microsoft) is the easiest and most frictionless variant. To save on 41 bucks by running...
Hi @galffing ,
I hope you don't mind me saying this, but based on the questions you've asked, it seems like W365 would be the best fit for your business needs.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Anything in the kernel logs about the interfaces maybe losing the connection? That could trigger the switch to the other interface.
If you do a multi-switch setup, the best approach would be to configure the two switches in an MLAG configuration...
Adding to @SteveITS bandwith is indeed important, if you can get to 25 or even 100gigs between sites..
You have to keep in mind that say, in RF4, each written block gets written to 4 places for safecopying, that's a lot
What is the speed and latency between the two locations? Hopefully 10 Gbit or higher? I could see this being very slow in several cases since at least 1/3 of all I/O is copied to the other data center.
4 nodes is more than 3 but you may want...
I agree with the others that this is a setup with many caveats and has high disk consumption (due to the requirement of having rf4)
Also this sounds like Corosync will be over shared media , so make sure your QoS is tight accordingly
Hey @abhijithiaaxin, welcome to the forum.
Whether it is a single-DC deployment or a split-DC deployment, you generally want an odd number of nodes in your cluster. But, as others have pointed out, a split-DC installation requires three...
As @gurubert already mentioned, you will need one node in a 3rd location.
Our Stretch Cluster guide has more details on how to get it up and running: https://pve.proxmox.com/wiki/Stretch_Cluster
You will have to span up a layer2 network between...