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 E4ED91FF17C for ; Wed, 17 Sep 2025 18:52:02 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D0D94B00C; Wed, 17 Sep 2025 18:52:15 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Date: Wed, 17 Sep 2025 18:52:02 +0200 Message-ID: <175812792035.2928616.18161306852011754697.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20250917163038.488710-1-f.ebner@proxmox.com> References: <20250917163038.488710-1-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1758127923571 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.153 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_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish 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] applied: [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" On Wed, 17 Sep 2025 18:30:24 +0200, Fiona Ebner wrote: > 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 :( > > [...] Applied, thanks! [1/6] partially fix #6805: api: clone: properly remove all snapshot-related info commit: 6572ff578488da700123281ac447d2ad6bd1771f [2/6] partially fix #6805: api: modify vm config: privilege checks for VM-state-related properties commit: 7c05f0be9858543272c1254c83f4dfc266b97fe2 [3/6] api: create/update: disallow setting 'running-nets-host-mtu' via API commit: f1fe3b748967d204c85960703407e0e655bfbb39 [4/6] resume from suspended: properly handle 'nets-host-mtu' commit: 80236b100e8cf5660b3f5f459e78e0ba322e1f21 [5/6] vm commandline: handle 'nets-host-mtu' property in snapshot commit: bd1a858f433e01dff8510173515004b3a91638e5 [6/6] vm start: remove left-over VM-state-related properties commit: 0db14e60109ea91a558f0f08594583588ef9ec66 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel