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 9978F1FF187 for ; Mon, 20 Oct 2025 11:49:48 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3565C420A; Mon, 20 Oct 2025 11:50:10 +0200 (CEST) Message-ID: <0e68a2ef-e09a-4da8-8e01-b72c62ebc3bd@proxmox.com> Date: Mon, 20 Oct 2025 11:49:36 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion , Laurent GUERBY References: <20251014143946.160679-1-f.ebner@proxmox.com> <20251014143946.160679-15-f.ebner@proxmox.com> <5eeef6c68d22ab2a6882ba3ee1bb852b1ae31108.camel@guerby.net> Content-Language: en-US From: Fiona Ebner In-Reply-To: <5eeef6c68d22ab2a6882ba3ee1bb852b1ae31108.camel@guerby.net> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1760953770815 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 Subject: Re: [pve-devel] [PATCH qemu-server 14/16] introduce QSD module for qemu-storage-daemon functionality 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" Hi, Am 20.10.25 um 10:57 AM schrieb Laurent GUERBY: > On Tue, 2025-10-14 at 16:39 +0200, Fiona Ebner wrote: >> For now, supports creating FUSE exports based on Proxmox VE drive >> definitions. NBD exports could be added later. In preparation to allow >> qcow2 for TPM state volumes. A QEMU storage daemon instance is >> associated to a given VM. > > Hi, > > I wonder if this addition of qemu-storage-daemon with fuse would be > able to solve the following issue I just opened: > > https://bugzilla.proxmox.com/show_bug.cgi?id=6953 > > "cannot set set-require-min-compat-client to reef, luminous clients > from kernel rbd due to VM with TPM /dev/rbd" > > The rbd kernel module feature is stuck to luminous Do you know why? Or if there is any interest to change that? > and swtpm use of > kernel /dev/rbd limits the usable features of the whole proxmox/ceph > cluster as soon as a VM with TPM is created on the cluster. > > If possible using qemu-storage-daemon to export the rbd image to swtpm > would still allow proxmox to leave the TPM disk on ceph while > benefiting from recent ceph features. It's would be possible, but it rather sounds like the real issue is that the kernel module is outdated. And for container volumes, krbd is also always used, so it would need to be adapted there too. Otherwise, you will still break container volumes when bumping the minimum required client version. > PS: ZFS over iSCSI isn't usable for TPM as well > https://bugzilla.proxmox.com/show_bug.cgi?id=3662 > TPM disfunctional with ZFS over iSCSI Yes, I'm planning to add that later, it's hopefully rather easy once the infrastructure is in place. Best Regards, Fiona _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel