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 2D5B61FF17C for ; Wed, 17 Sep 2025 18:30:35 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6E7FFA771; Wed, 17 Sep 2025 18:30:47 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Wed, 17 Sep 2025 18:30:24 +0200 Message-ID: <20250917163038.488710-1-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.2 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1758126634279 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.024 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 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [qemu.pm, qemuserver.pm] Subject: [pve-devel] [PATCH-SERIES qemu-server 0/6] VM-state property handling improvements 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" Fix bug #6805, fix handling nets-host-mtu in more contexts like resume from hibernation and printing the commandline of a snapshot. Disallow setting that property by a user via API like is done for other VM-state properties. Sorry, I thought I had checked for all occurences of 'runningmachine' when introducing 'running-nets-host-mtu', but apparently I missed some in the QemuServer module :( Also introduce proper privilege checking for VM-state properties. Finally, detect and cleanup such properties upon VM start. I haven't come around to testing these for stable-bookworm yet, but will let you know if they apply/work cleanly there too. Fiona Ebner (6): partially fix #6805: api: clone: properly remove all snapshot-related info partially fix #6805: api: modify vm config: privilege checks for VM-state-related properties api: create/update: disallow setting 'running-nets-host-mtu' via API resume from suspended: properly handle 'nets-host-mtu' vm commandline: handle 'nets-host-mtu' property in snapshot vm start: remove left-over VM-state-related properties src/PVE/API2/Qemu.pm | 9 +++++++-- src/PVE/QemuServer.pm | 24 ++++++++++++++++++++++-- 2 files changed, 29 insertions(+), 4 deletions(-) -- 2.47.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel