From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 886BF98877 for ; Tue, 25 Apr 2023 18:52:43 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6E2B63E855 for ; Tue, 25 Apr 2023 18:52:43 +0200 (CEST) Received: from bastionodiso.odiso.net (bastionodiso.odiso.net [185.151.191.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 25 Apr 2023 18:52:42 +0200 (CEST) Received: from kvmformation3.odiso.net (formationkvm3.odiso.net [10.3.94.12]) by bastionodiso.odiso.net (Postfix) with ESMTP id D29598175; Tue, 25 Apr 2023 18:52:33 +0200 (CEST) Received: by kvmformation3.odiso.net (Postfix, from userid 0) id B9B7D350BD; Tue, 25 Apr 2023 18:52:33 +0200 (CEST) From: Alexandre Derumier To: pve-devel@lists.proxmox.com Date: Tue, 25 Apr 2023 18:52:31 +0200 Message-Id: <20230425165233.3745210-1-aderumier@odiso.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.015 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 HEADER_FROM_DIFFERENT_DOMAINS 0.25 From and EnvelopeFrom 2nd level mail domains are different KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [qemumigrate.pm, qm.pm, qemu.pm] Subject: [pve-devel] [PATCH v2 qemu-server 0/2] remote-migration: migration with different cpu 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: , X-List-Received-Date: Tue, 25 Apr 2023 16:52:43 -0000 This patch series allow remote migration between cluster with different cpu model. A new param is introduced: "target-cpu" When target-cpu is defined, the live migration with memory transfert is skipped (as anyway, the target will die with a different cpu). Then, after the storage copy, we call agent fsfreeze or suspend the vm to have coherent data. Then we stop the source vm and stop/start the target vm. Like this, we can reduce the downtime of migration to only 1 restart. Changelog v2: The first version was simply shuting down the target vm, wihout doing the block-job-complete. After doing production migration with around 400vms, I had some fs corruption, like some datas was still in buffer. This v2 has been tested with another 400vms batch, without any corruption. Alexandre Derumier (2): migration: move livemigration code in a dedicated sub remote-migration: add target-cpu param PVE/API2/Qemu.pm | 18 ++ PVE/CLI/qm.pm | 6 + PVE/QemuMigrate.pm | 439 ++++++++++++++++++++++++--------------------- 3 files changed, 260 insertions(+), 203 deletions(-) -- 2.30.2