public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Michal Fox <me@dualfroz.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs] fix #5273: pvecm: qdevice: note to not run qnetd on the cluster itself
Date: Sun,  4 Oct 2026 15:33:11 +0000	[thread overview]
Message-ID: <20261004153311.7-1-me@dualfroz.com> (raw)

The section about the external vote support already says that the vote
daemon runs on an independent server, but does not spell out that this
rules out running it on the cluster itself, for example on one of the
nodes or in a guest, which might look like an easy option for a cluster
with only two nodes.

Add a note that says so explicitly, and why: if the node running the
daemon fails, the cluster loses two votes at once, and a guest running
it cannot be started without quorum, as starting a guest requires a
quorate cluster.

Signed-off-by: Michal Fox <me@dualfroz.com>
---

Notes:
    that guests cannot be started without quorum is based on the quorum
    check in the start API calls of qemu-server and pve-container. rendered
    the chapter with asciidoc, without new warnings.

 pvecm.adoc | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/pvecm.adoc b/pvecm.adoc
index 8309647..ac4e92f 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1132,6 +1132,13 @@ For this to work, there are two services involved:
 As a result, you can achieve higher availability, even in smaller setups (for
 example 2+1 nodes).
 
+NOTE: The server running the external vote daemon must not be part of the
+cluster in any form. Do not run the daemon on a node of the same cluster, nor
+in a virtual machine or container on it. Otherwise, if the node running the
+daemon fails, the cluster loses the vote of this node and the one of the
+QDevice at the same time. Also, a guest running the daemon cannot be started
+while the cluster is not quorate.
+
 QDevice Technical Overview
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- 
2.43.0




                 reply	other threads:[~2026-10-04 15:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261004153311.7-1-me@dualfroz.com \
    --to=me@dualfroz.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal