From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 5FEB11FF183 for ; Wed, 24 Sep 2025 16:48:59 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A975BB176; Wed, 24 Sep 2025 16:49:26 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Wed, 24 Sep 2025 16:47:11 +0200 Message-ID: <20250924144848.170589-3-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20250924144848.170589-1-f.ebner@proxmox.com> References: <20250924144848.170589-1-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1758725318658 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.272 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 KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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 qemu 2/5] bump baseline machine version to 6.0 for Proxmox VE 9 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" This was missed with QEMU 10.0 and should've been bumped already for the release of Proxmox VE 9 to get more complete deprecation warnings. The compile time check for detecting too old baseline is only active starting with QEMU 10.1, since the new policy on the QEMU side is enforced starting with that version and that's why it slipped through. Signed-off-by: Fiona Ebner --- ...043-adapt-machine-version-deprecation-for-Proxmox-VE.patch | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/patches/pve/0043-adapt-machine-version-deprecation-for-Proxmox-VE.patch b/debian/patches/pve/0043-adapt-machine-version-deprecation-for-Proxmox-VE.patch index 6e587fa..9d0d5d1 100644 --- a/debian/patches/pve/0043-adapt-machine-version-deprecation-for-Proxmox-VE.patch +++ b/debian/patches/pve/0043-adapt-machine-version-deprecation-for-Proxmox-VE.patch @@ -47,8 +47,8 @@ index 8ada4d5832..f9f3b75284 100644 + * 9 11.2 5.2 and older 6.0 + * 10 13.2 7.2 and older 8.0 + */ -+#define MACHINE_VER_BASELINE_PVE_MAJOR 2 -+#define MACHINE_VER_BASELINE_PVE_MINOR 4 ++#define MACHINE_VER_BASELINE_PVE_MAJOR 6 ++#define MACHINE_VER_BASELINE_PVE_MINOR 0 +#define MACHINE_VER_DELETION_MAJOR (QEMU_VERSION_MAJOR - 6) +#define MACHINE_VER_DELETION_MINOR QEMU_VERSION_MINOR + -- 2.47.3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel