[pve-devel] [PATCH qemu-server 0/2] set write threshold logic

[Tiago Sousa via pve-devel <pve-devel@lists.proxmox.com>]

[-- Attachment #1: Type: message/rfc822, Size: 5300 bytes --]

From: Tiago Sousa <joao.sousa@eurotux.com>
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>

Hello,

I'm looking for some assistance in understanding why the block_write_threshold
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 not,
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 seem
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



[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel