Search results

I'm querying PVE API to monitor resource usage with Zabbix. And I'm wondering, why does the maxdisk prop (in /cluster/resources or /pools/<pool name> for example) only accounts the size of the boot disk ? Wouldn't it make more sense to sum all the disks attached to the VM / attached to VM of the...

Check on the wiki. There's an agent pong command to check it's working. If you can't have the agent working just disable the agent option so proxmox send a simple acpi signal.

Have you enabled the qemu agent option ? If yes, you need to install the agent in the guests so they can shut down cleanly

No it doesn't

Thx for the missing .conf I've fixed it. Can you elaborate for the permission issue ? And for Background false, it's on purpose. The systemd unit created are of type simple, so thge daemopn must not double fork to run in the background

redundant != HA. To prevent splitbrains, only the quorate part of the cluster (which means at least half + 1 node) can run VM. The other nodes are self fenced automatically. With only two nodes, both would lost the quorum at the same time, and none can decide to operate. You can probably trick...

HA makes no sense with less than 3 nodes. The cluster needs to be quorate, which requires a minimum of 3 nodes. So, unless you can add a 3rd node, you should remove the HA resource. Leaving the HA stuff appart, I don't know why a simple migrate would work from the CLI with qm and not from the web

You need at least 3 nodes to have HA. Remove HA, and you should be able to migrate from the web GUI (manually only)

Because we need a DKIM verifier which adds needed headers so that DMARC can act, and reject the mail if it's the sender's policy. spamassassin DKIm verifier just adjust score (and usually, it just adds (or remove when valid) a tiny 0.1 or similar)