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 1284A1FF146 for ; Tue, 20 Jan 2026 18:21:26 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0109915D7A; Tue, 20 Jan 2026 18:21:40 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Date: Tue, 20 Jan 2026 18:21:27 +0100 Message-ID: <176892968302.1489097.1806503031752629838.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251201135345.125993-1-f.ebner@proxmox.com> References: <20251201135345.125993-1-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1768929641093 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.021 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. [proxmox.com] Subject: [pve-devel] applied: [PATCH qemu-server] migration: prohibit renaming cloud-init drive 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 Mon, 01 Dec 2025 14:51:54 +0100, Fiona Ebner wrote: > Usually, disks are allowed to be renamed during migration if there is > a naming conflict caused by a left-over disk on the target. However, > the type of the cloud-init disk is encoded in its name, so it must not > be renamed or it cannot be recognized as a cloud-init disk anymore, as > reported in the community forum [0]. > > [0]: https://forum.proxmox.com/threads/167767/ > > [...] Applied, thanks! [1/1] migration: prohibit renaming cloud-init drive commit: ea906cf6f32808f3f376b794c8c9e5cd95019d47 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel