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 930531FF187 for ; Mon, 20 Oct 2025 16:13:24 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 20508A718; Mon, 20 Oct 2025 16:13:44 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Mon, 20 Oct 2025 16:12:50 +0200 Message-ID: <20251020141335.124077-4-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251020141335.124077-1-f.ebner@proxmox.com> References: <20251020141335.124077-1-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1760969613884 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.022 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] [PATCH storage v2 03/16] common: add pve-vm-image-format standard option for VM image formats 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" The image formats defined for the pve-vm-image-format standard option are the formats that are allowed on Proxmox VE storages for VM images. Signed-off-by: Fiona Ebner Reviewed-by: Daniel Kral Tested-by: Daniel Kral --- src/PVE/Storage/Common.pm | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/src/PVE/Storage/Common.pm b/src/PVE/Storage/Common.pm index 222dc76..3932aee 100644 --- a/src/PVE/Storage/Common.pm +++ b/src/PVE/Storage/Common.pm @@ -45,16 +45,31 @@ Possible formats a guest image can have. =cut +PVE::JSONSchema::register_standard_option( + 'pve-storage-image-format', + { + type => 'string', + enum => ['raw', 'qcow2', 'subvol', 'vmdk'], + description => "Format of the image.", + }, +); + +=head3 pve-vm-image-format + +Possible formats a VM image can have. + +=cut + # TODO PVE 9 - Note that currently, qemu-server allows more formats for VM images, so third party # storage plugins might potentially allow more too, but none of the plugins we are aware of do that. # Those formats should either be allowed here or support for them should be phased out (at least in # the storage layer). Can still be added again in the future, should any plugin provider request it. PVE::JSONSchema::register_standard_option( - 'pve-storage-image-format', + 'pve-vm-image-format', { type => 'string', - enum => ['raw', 'qcow2', 'subvol', 'vmdk'], + enum => ['raw', 'qcow2', 'vmdk'], description => "Format of the image.", }, ); -- 2.47.3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel