[pve-devel] [PATCH docs 1/2] VM live migration: mention that CPU vendor should be the same

[pve-devel] [PATCH docs 1/2] VM live migration: mention that CPU vendor should be the same

[Fabian Ebner]

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

[pve-devel] [PATCH docs 2/2] cluster: migration: use back-ticked insecure when referring to the setting

[Fabian Ebner]

Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
---
 pvecm.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pvecm.adoc b/pvecm.adoc
index 26b52cf..48c3927 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1273,7 +1273,7 @@ Migration Type
 
 The migration type defines if the migration data should be sent over an
 encrypted (`secure`) channel or an unencrypted (`insecure`) one.
-Setting the migration type to insecure means that the RAM content of a
+Setting the migration type to `insecure` means that the RAM content of a
 virtual guest is also transferred unencrypted, which can lead to
 information disclosure of critical data from inside the guest (for
 example, passwords or encryption keys).
@@ -1286,7 +1286,7 @@ NOTE: Storage migration does not follow this setting. Currently, it
 always sends the storage content over a secure channel.
 
 Encryption requires a lot of computing power, so this setting is often
-changed to "unsafe" to achieve better performance. The impact on
+changed to `insecure` to achieve better performance. The impact on
 modern systems is lower because they implement AES encryption in
 hardware. The performance impact is particularly evident in fast
 networks, where you can transfer 10 Gbps or more.
-- 
2.30.2

[pve-devel] applied-series: [PATCH docs 1/2] VM live migration: mention that CPU vendor should be the same

[Thomas Lamprecht]

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

applied both patches, thanks!