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 AF45B1FF16B for ; Thu, 20 Feb 2025 15:29:25 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 43BD3147E1; Thu, 20 Feb 2025 15:29:19 +0100 (CET) Message-ID: <2f259144-b0a9-4cf8-8273-ea9f29c0777a@proxmox.com> Date: Thu, 20 Feb 2025 15:29:15 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion , Daniel Kral References: <20250211160825.254167-1-d.kral@proxmox.com> <20250211160825.254167-13-d.kral@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <20250211160825.254167-13-d.kral@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.045 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: Re: [pve-devel] [PATCH qemu-server v2 07/15] fix #5284: cli: importovf: assert content type support for target storage 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" Am 11.02.25 um 17:08 schrieb Daniel Kral: > Asserts whether the target storage supports storing VM images before > importing a OVF manifest as a VM to the target storage. > > Without the check in place, a VM volume can be imported to a storage, > which does not support VM images, but won't be able to start since any > attached volume must be stored on a supported storage. > > Signed-off-by: Daniel Kral Reviewed-by: Fiona Ebner > --- > changes since v1: > - new! (was fixed without special notice in rfc, now it's more obvious) > > PVE/CLI/qm.pm | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/PVE/CLI/qm.pm b/PVE/CLI/qm.pm > index 4214a7ca..58167050 100755 > --- a/PVE/CLI/qm.pm > +++ b/PVE/CLI/qm.pm > @@ -756,7 +756,9 @@ __PACKAGE__->register_method ({ > > die "$ovf_file: non-existent or non-regular file\n" if (! -f $ovf_file); > my $storecfg = PVE::Storage::config(); > - PVE::Storage::storage_check_enabled($storecfg, $storeid); > + my $scfg = PVE::Storage::storage_check_enabled($storecfg, $storeid); > + raise_param_exc({ storage => "storage '$storeid' does not support vm images" }) > + if !$scfg->{content}->{images}; > > my $parsed = PVE::GuestImport::OVF::parse_ovf($ovf_file); > _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel