From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 793D61FF189 for <inbox@lore.proxmox.com>; Fri, 4 Apr 2025 09:31:24 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7CABCFB14; Fri, 4 Apr 2025 09:31:10 +0200 (CEST) Message-ID: <ca8d6f7d-6ae9-4843-8a56-53d818e61502@proxmox.com> Date: Fri, 4 Apr 2025 09:30:32 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Friedrich Weber <f.weber@proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com> References: <20250401173435.221892-1-f.ebner@proxmox.com> <587b5ac2-1f8b-437b-91e6-52a4b5142235@proxmox.com> Content-Language: en-US From: Fiona Ebner <f.ebner@proxmox.com> In-Reply-To: <587b5ac2-1f8b-437b-91e6-52a4b5142235@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.038 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-SERIES qemu/storage/qemu-server/container/manager v7 00/37] backup provider API X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> Am 02.04.25 um 17:15 schrieb Friedrich Weber: > - I needed to install nbdfuse and modprobe nbd -- might be nice to do > both automatically somehow (though packages of external backup plugins > could probably add nbdfuse as a dependency?) No, modprobe nbd is really only needed for the POC testing of the NBD mechanism in the dir example plugin, and is deliberately not done automatically anymore (was in an earlier version when it was also needed in qemu-server, but nowadays it isn't anymore). People not using any external backup provider don't need nbdfuse either, so it doesn't make sense to pull it for everybody IMHO. I mean, if we really want to we could add it as recommended. We might even throw out the NBD mechanism in the dir example plugin, since Wolfgang has done it properly in his. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel