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 B6C4A1FF161 for ; Sat, 2 Aug 2025 18:41:32 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0782192B4; Sat, 2 Aug 2025 18:42:59 +0200 (CEST) To: pve-devel@lists.proxmox.com Date: Sat, 2 Aug 2025 17:42:38 +0100 In-Reply-To: References: MIME-Version: 1.0 Message-ID: List-Id: Proxmox VE development discussion List-Post: From: Tiago Sousa via pve-devel Precedence: list Cc: Tiago Sousa X-Mailman-Version: 2.1.29 X-BeenThere: pve-devel@lists.proxmox.com List-Subscribe: , List-Unsubscribe: , List-Archive: Reply-To: Proxmox VE development discussion List-Help: Subject: [pve-devel] [PATCH qemu-server 0/2] set write threshold logic Content-Type: multipart/mixed; boundary="===============6808354403769877967==" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" --===============6808354403769877967== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: X-Original-To: pve-devel@lists.proxmox.com Delivered-To: pve-devel@lists.proxmox.com Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 17B35D09E5 for ; Sat, 2 Aug 2025 18:42:57 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F20519242 for ; Sat, 2 Aug 2025 18:42:56 +0200 (CEST) Received: from eurotux.com (mail.eurotux.com [185.98.249.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Sat, 2 Aug 2025 18:42:55 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by eurotux.com (Postfix) with ESMTP id D99DC30CA7DD; Sat, 2 Aug 2025 17:42:45 +0100 (WEST) Authentication-Results: mail.prd.eurotux.pt (amavisd-new); dkim=pass (2048-bit key) reason="pass (just generated, assumed good)" header.d=eurotux.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eurotux.com; h= content-transfer-encoding:mime-version:references:in-reply-to :x-mailer:message-id:date:date:subject:subject:from:from; s= default; t=1754152965; x=1755967366; bh=MhSmMBqHqmZfMBIL61hWIW4j JyoWbPfpj9w6UghfDAU=; b=KQ5Ks489k5DZrX7nZ5TIFORQnq6YsAvzPbmhjIlZ p+TdY3XgwBwyVklqCp1idmLnasxBByXxLkBkh9uU21MuoVtRWCvSJvNz0xy+Jd5C Wv8EZbPXkxF6KnfD8PQdYpKfbAeRIqBvceok5Xpc8AFDmh4Q6HEwfywUuRwXcW84 CRbZltGt4tYkGhX/myIalJpdM0BHF3NQFYGGCKcDgmjsbu+Evql93nAfPsOVs6gb q9W+Qhvlr2Gh+/XyYRrf9dBKPnldl2VC0tsEpK9PUGmgte+vDXZsrA9DYZLKcwx2 uhNwyhE8NxvWxXzITbuVX4OgTqdwuYNI9v0gd1NO9zWiyg== X-Virus-Scanned: amavisd-new at mail.prd.eurotux.pt Received: from eurotux.com ([127.0.0.1]) by localhost (mail.prd.eurotux.pt [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hxLFHI17g2dK; Sat, 2 Aug 2025 17:42:45 +0100 (WEST) Received: from proxmox.example (unknown [161.230.225.89]) (Authenticated sender: joao.sousa@eurotux.com) by eurotux.com (Postfix) with ESMTPSA id 58D6D30C6F9D; Sat, 2 Aug 2025 17:42:45 +0100 (WEST) From: Tiago Sousa To: pve-devel@lists.proxmox.com Subject: [PATCH qemu-server 0/2] set write threshold logic Date: Sat, 2 Aug 2025 17:42:38 +0100 Message-Id: <20250802164240.21751-1-joao.sousa@eurotux.com> X-Mailer: git-send-email 2.39.5 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.049 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy RCVD_IN_MSPIKE_H2 0.001 Average reputation (+2) 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_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [blockdev.pm,eurotux.com] Hello, I'm looking for some assistance in understanding why the block_write_thre= shold is not being set as expected. When the VM starts and I run the query-named-block-nodes command, the write_threshold value always appears as the default 0. However, if I set = it manually through the QMP socket after startup, the threshold is applied correctly. Is the attach function not the appropriate place to set this value? If no= t, could you clarify the correct point in the VM startup sequence to set it?= I had assumed it would be applied during blockdev_add, but that doesn't see= m to be the case. Any guidance would be appreciated. Tiago Sousa (2): blockdev: add set write threshold qmeventd: add block write threshold event handling src/PVE/QemuServer/Blockdev.pm | 52 ++++++++++++++++++++++++++++++++++ src/qmeventd/qmeventd.c | 19 +++++++++++++ 2 files changed, 71 insertions(+) -- 2.39.5 --===============6808354403769877967== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel --===============6808354403769877967==--