all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Erik Fastermann <e.fastermann@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Erik Fastermann <e.fastermann@proxmox.com>
Subject: [PATCH pve-docs 3/3] partially fix #1989: qm: document qcow2 cache size config
Date: Fri,  5 Jun 2026 17:35:12 +0200	[thread overview]
Message-ID: <20260605153512.265703-4-e.fastermann@proxmox.com> (raw)
In-Reply-To: <20260605153512.265703-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 | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/qm.adoc b/qm.adoc
index e6b7918..2f1e7d4 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -341,6 +341,16 @@ 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_hard_disk_qcow2_cache]]
+Cache Size (qcow2)
+^^^^^^^^^^^^^^^^^^
+Fine-tuning the qcow2 L2/refcount cache behavior can provide significant
+performance gains. 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 configure the cache
+size directly or let Proxmox VE automatically choose a cache size based on the
+disk image size. All other options can be managed with the API.
+
 [[qm_cpu]]
 CPU
 ~~~
-- 
2.47.3




      parent reply	other threads:[~2026-06-05 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05 15:35 [PATCH docs/manager/qemu-server 0/3] partially fix #1989: add QEMU qcow2 cache options Erik Fastermann
2026-06-05 15:35 ` [PATCH qemu-server 1/3] partially fix #1989: disk: add " Erik Fastermann
2026-06-05 15:35 ` [PATCH pve-manager 2/3] partially fix #1989: ui: qemu: disk: add qcow2 cache size config Erik Fastermann
2026-06-05 15:35 ` 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=20260605153512.265703-4-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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal