From: Erik Fastermann <e.fastermann@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Erik Fastermann <e.fastermann@proxmox.com>
Subject: [PATCH pve-docs v3 6/6] partially fix #1989: qm: document qcow2 cache size config
Date: Fri, 16 Oct 2026 14:26:02 +0200 [thread overview]
Message-ID: <20261016122602.183911-7-e.fastermann@proxmox.com> (raw)
In-Reply-To: <20261016122602.183911-1-e.fastermann@proxmox.com>
Add a new subsection to document the new qcow2 cache config options.
Signed-off-by: Erik Fastermann <e.fastermann@proxmox.com>
---
qm.adoc | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/qm.adoc b/qm.adoc
index 18a4fbe..0c5d91d 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -350,6 +350,22 @@ 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_hard_disk_qcow2_cache]]
+Cache Size (qcow2)
+^^^^^^^^^^^^^^^^^^
+Fine-tuning the qcow2 L2/refcount cache behavior can provide significant
+performance gains for large disks. See the
+https://gitlab.com/qemu-project/qemu/-/blob/master/docs/qcow2-cache.txt[QEMU documentation]
+for a detailed explanation of these options. You can either set the cache size
+directly or let {pve} choose it automatically based on the disk image size. When
+sizing the cache automatically, with the default 64 KiB cluster size, 16
+refcount bits and no extended L2 entries, the cache uses at most roughly 160 KiB
+of memory per GiB of disk. The remaining options (`qcow2-l2-cache-size`,
+`qcow2-refcount-cache-size`, `qcow2-l2-cache-entry-size` and
+`qcow2-cache-clean-interval`) can be set with `qm set` or through the API. The
+cache is allocated by the QEMU process in addition to the memory assigned to the
+guest.
+
[[qm_cpu]]
CPU
~~~
--
2.47.3
prev parent reply other threads:[~2026-10-16 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 12:25 [PATCH docs/manager/qemu-server v3 0/6] partially fix #1989: add QEMU qcow2 cache options Erik Fastermann
2026-10-16 12:25 ` [PATCH qemu-server v3 1/6] re-tidy source code Erik Fastermann
2026-10-16 12:25 ` [PATCH qemu-server v3 2/6] drive: fix conversion of bps throttle limits to mbps Erik Fastermann
2026-10-16 12:25 ` [PATCH qemu-server v3 3/6] api: report why drive options are rejected Erik Fastermann
2026-10-16 12:26 ` [PATCH qemu-server v3 4/6] partially fix #1989: disk: add qcow2 cache options Erik Fastermann
2026-10-16 12:26 ` [PATCH pve-manager v3 5/6] partially fix #1989: ui: qemu: disk: add qcow2 cache size config Erik Fastermann
2026-10-16 12:26 ` Erik Fastermann [this message]
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=20261016122602.183911-7-e.fastermann@proxmox.com \
--to=e.fastermann@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.