From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 1/1] qm: clarify when the iothreads options takes into effect
Date: Wed, 19 Aug 2026 10:32:11 +0200 [thread overview]
Message-ID: <20260819083214.115093-1-m.sandoval@proxmox.com> (raw)
The main point addressed is that the "VirtIO Block" bus controller type was
referred as "VirtIO". This can be a source of confusion since the are multiple
controllers for different components provided by VirtIO.
VirtIO SCSI is listed before VirtIO Block as a soft-recommendation.
We use the same terms as the web UI, modulo capitalization for "Bus/Device" and
"SCSI Controller".
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
qm.adoc | 20 ++++++++++++--------
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/qm.adoc b/qm.adoc
index 5b46cdc..51935ea 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -337,14 +337,18 @@ Note that *SSD emulation* is not supported on *VirtIO Block* drives.
[[qm_hard_disk_iothread]]
IO Thread
^^^^^^^^^
-The option *IO Thread* can only be used when using a disk with the *VirtIO*
-controller, or with the *SCSI* controller, when the emulated controller type is
-*VirtIO SCSI single*. With *IO Thread* enabled, QEMU creates one I/O thread per
-storage controller rather than handling all I/O in the main event loop or vCPU
-threads. One benefit is better work distribution and utilization of the
-underlying storage. Another benefit is reduced latency (hangs) in the guest for
-very I/O-intensive host workloads, since neither the main thread nor a vCPU
-thread can be blocked by disk I/O.
+The *IO thread* option can only be used when using a disk with one of the
+following bus/device controllers:
+
+* *SCSI*, if the emulated SCSI controller type is *VirtIO SCSI single*, or
+* *VirtIO Block*
+
+With *IO thread* enabled, QEMU creates one I/O thread per storage controller
+rather than handling all I/O in the main event loop or vCPU threads. One benefit
+is better work distribution and utilization of the underlying storage. Another
+benefit is reduced latency (hangs) in the guest for very I/O-intensive host
+workloads, since neither the main thread nor a vCPU thread can be blocked by
+disk I/O.
[[qm_cpu]]
CPU
--
2.47.3
next reply other threads:[~2026-08-19 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 8:32 Maximiliano Sandoval [this message]
2026-08-20 15:18 ` [PATCH docs 1/1] qm: clarify when the iothreads options takes into effect Abobakr Mohammed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260819083214.115093-1-m.sandoval@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.