From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 152821FF165 for ; Thu, 3 Jul 2025 13:57:11 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 97BAC122AB; Thu, 3 Jul 2025 13:57:05 +0200 (CEST) From: Christoph Heiss To: pve-devel@lists.proxmox.com Date: Thu, 3 Jul 2025 13:54:16 +0200 Message-ID: <20250703115621.883244-15-c.heiss@proxmox.com> X-Mailer: git-send-email 2.49.0 In-Reply-To: <20250703115621.883244-1-c.heiss@proxmox.com> References: <20250703115621.883244-1-c.heiss@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.030 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs v3 14/14] qm: document conntrack state migration for live migrations X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Signed-off-by: Christoph Heiss --- Changes v2 -> v3: * new patch qm.adoc | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/qm.adoc b/qm.adoc index 8b9e096..823e818 100644 --- a/qm.adoc +++ b/qm.adoc @@ -1664,6 +1664,22 @@ For Live Migration to work, there are some things required: configured, but it cannot be guaranteed - so please test before deploying such a setup in production. +Conntrack State Migration +^^^^^^^^^^^^^^^^^^^^^^^^^ + +NOTE: Conntrack state migration is considered best-effort only and might not +work, as it heavily depends on the network setup. + +Conntrack is a Linux kernel mechanism to enable a stateful firewall by tracking +individual connection. When live migrating running VMs, active in- and/or +outbound connections *might* get interrupted as soon as the VM starts running on +the target host, as the new host node does not have the same conntrack entries +and thus the firewall can drop packets. + +Conntrack state migration copies all conntrack entries on the host for the +live-migrated VM to the target node and afterwards flushes the migrated entries +from the conntrack table on the source node. + Offline Migration ~~~~~~~~~~~~~~~~~ -- 2.49.0 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel