From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2 1/5] pvecm: drop notes about old version incompatibilities
Date: Fri, 27 Jun 2025 15:44:49 +0200 [thread overview]
Message-ID: <20250627134455.2065020-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20250627134455.2065020-1-a.lauterer@proxmox.com>
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pvecm.adoc | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index 18f7389..47e42e2 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -77,18 +77,6 @@ Requirements
* Online migration of virtual machines is only supported when nodes have CPUs
from the same vendor. It might work otherwise, but this is never guaranteed.
-NOTE: It is not possible to mix {pve} 3.x and earlier with {pve} 4.X cluster
-nodes.
-
-NOTE: While it's possible to mix {pve} 4.4 and {pve} 5.0 nodes, doing so is
-not supported as a production configuration and should only be done temporarily,
-during an upgrade of the whole cluster from one major version to another.
-
-NOTE: Running a cluster of {pve} 6.x with earlier versions is not possible. The
-cluster protocol (corosync) between {pve} 6.x and earlier versions changed
-fundamentally. The corosync 3 packages for {pve} 5.4 are only intended for the
-upgrade procedure to {pve} 6.0.
-
Preparing Nodes
---------------
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-06-27 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 13:44 [pve-devel] [PATCH docs/manager v2 0/7] by expanding on it in the docs and the UI Aaron Lauterer
2025-06-27 13:44 ` Aaron Lauterer [this message]
2025-07-16 23:04 ` [pve-devel] partially-applied: [PATCH docs v2 1/5] pvecm: drop notes about old version incompatibilities Thomas Lamprecht
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 2/5] pvecm: add anchor for cluster requirements Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 3/5] pvecm: add anchor for corosync exernal vote support Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 4/5] pvecm: extend cluster Requirements Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 5/5] ha-manager: expand requirements Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH manager v2 1/2] ui: cluster create: add recommendations for cluster networks Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH manager v2 2/2] ui: guest import: make sure an external link has target _blank Aaron Lauterer
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=20250627134455.2065020-2-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.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