From: Marco Gaiarin <gaio@lilliput.linux.it>
To: dorsy via pve-user <pve-user@lists.proxmox.com>
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Quorum bouncing, VM does not start...
Date: Mon, 25 Aug 2025 11:04:49 +0200 [thread overview]
Message-ID: <filtnl-1fq.ln1@leia.lilliput.linux.it> (raw)
In-Reply-To: <mailman.179.1755644682.385.pve-user@lists.proxmox.com>; from SmartGate on Mon, Aug 25, 2025 at 20:06:01PM +0200
Mandi! dorsy via pve-user
In chel di` si favelave...
> I'd suggest a direct link between the hosts for another quorum ring if
> You have a spare network port.
> Also multiple rings could be more resilient than MLAG. But that is only
> my 2 cents opinion.
> see: https://pve.proxmox.com/pve-docs/chapter-pvecm.html#pvecm_redundancy
> and:
> https://pve.proxmox.com/pve-docs/chapter-pvecm.html#pvecm_corosync_over_bonds
Thans for the links. Seems to me that also 'LACP fast' is a pretty decent
solution for that!
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2025-08-25 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 15:08 Marco Gaiarin
2025-08-19 22:53 ` dorsy via pve-user
2025-08-25 9:04 ` Marco Gaiarin [this message]
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=filtnl-1fq.ln1@leia.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@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