all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/2] VM live migration: mention that CPU vendor should be the same
Date: Wed, 17 Nov 2021 14:05:00 +0100	[thread overview]
Message-ID: <20211117130501.69274-1-f.ebner@proxmox.com> (raw)

Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
---
 pvecm.adoc | 3 +++
 qm.adoc    | 2 ++
 2 files changed, 5 insertions(+)

diff --git a/pvecm.adoc b/pvecm.adoc
index 0b1857e..26b52cf 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -74,6 +74,9 @@ Requirements
 
 * The root password of a cluster node is required for adding nodes.
 
+* 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.
 
diff --git a/qm.adoc b/qm.adoc
index 37ea439..b1e22f9 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1154,6 +1154,8 @@ For Live Migration to work, there are some things required:
 * The hosts have a working (and reliable) network connection.
 * The target host must have the same or higher versions of the
   {pve} packages. (It *might* work the other way, but this is never guaranteed)
+* The hosts have CPUs from the same vendor. (It *might* work otherwise, but this
+  is never guaranteed)
 
 Offline Migration
 ~~~~~~~~~~~~~~~~~
-- 
2.30.2





             reply	other threads:[~2021-11-17 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 13:05 Fabian Ebner [this message]
2021-11-17 13:05 ` [pve-devel] [PATCH docs 2/2] cluster: migration: use back-ticked insecure when referring to the setting Fabian Ebner
2021-11-17 14:34 ` [pve-devel] applied-series: [PATCH docs 1/2] VM live migration: mention that CPU vendor should be the same Thomas Lamprecht

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=20211117130501.69274-1-f.ebner@proxmox.com \
    --to=f.ebner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal