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 53F581FF179 for ; Wed, 12 Nov 2025 15:23:35 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7060253A2; Wed, 12 Nov 2025 15:24:19 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Friedrich Weber Date: Wed, 12 Nov 2025 15:23:35 +0100 Message-ID: <176295741278.1175891.2811462476320479030.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251111123222.73957-1-f.weber@proxmox.com> References: <20251111123222.73957-1-f.weber@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1762957400305 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.026 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 Subject: [pve-devel] applied: [PATCH qemu-server v2] clone disk: fix handling of snapshot-as-volume-chain for EFI disks 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 Tue, 11 Nov 2025 13:09:30 +0100, Friedrich Weber wrote: > Currently, cloning an EFI disk off a snapshot-as-volume-chain snapshot > fails with "qemu-img: Failed to load snapshot: Can't find snapshot". > The reason is that the special case for EFI disks calls `qemu-img dd` > with the additional `-l snapname` option, which is only valid for > qcow2-internal snapshots. For snapshot-as-volume-chain snapshots, the > source volume is already the volume corresponding to the snapshot. > > [...] Applied, thanks! [1/1] clone disk: fix handling of snapshot-as-volume-chain for EFI disks commit: 08ec0fddede24065cd850eabe9fa7a79c93d45df _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel