From: "Lukas Sichert" <l.sichert@proxmox.com>
To: "Christian Ebner" <c.ebner@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH v4 qemu-server 2/3] pbs-restore: set 'no-cache' on block devices backed by zfspool
Date: Fri, 21 Aug 2026 09:44:41 +0200 [thread overview]
Message-ID: <DKUGD3A91QKA.GJF8R0HPVWIJ@proxmox.com> (raw)
In-Reply-To: <20260820131049.374072-3-c.ebner@proxmox.com>
On 2026-08-20 15:10, Christian Ebner <c.ebner@proxmox.com> wrote:
> Skip the host page cache for restores on zvols, as page writeback
> after filling the buffers can cause I/O delay on other ZFS-backed VMs
> on certain setups, as reported in enterprise support and reproduced
> internally. The restored data is not to be read back from cache
> during restore anyways.
>
> Keep for other storage types for now to reduce regression potential.
>
> Version bump in d/control assures feature compatibility for
> pbs-restore.
>
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
When I tried to install qemu-server with pve-qemu-kvm at 11.0.3-2
APT aborted the installation due to unsatisfied dependencies.
With pve-qemu-kvm bumped to 11.0.3-3 the installation was possible
and the --no-cache flag was set correctly.
Also my +local suffixes did not create any issues.
Therefore, consider this:
Tested-by: Lukas Sichert <l.sichert@proxmox.com>
next prev parent reply other threads:[~2026-08-21 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 13:10 [PATCH v4 pve-qemu qemu-server 0/3] bypass host page cache for restore on zvol Christian Ebner
2026-08-20 13:10 ` [PATCH v4 pve-qemu 1/3] pbs-restore: add optional no-cache flag to bypass host page cache Christian Ebner
2026-08-20 13:10 ` [PATCH v4 qemu-server 2/3] pbs-restore: set 'no-cache' on block devices backed by zfspool Christian Ebner
2026-08-21 7:44 ` Lukas Sichert [this message]
2026-08-20 13:10 ` [PATCH v4 qemu-server 3/3] vma restore: skip page cache " Christian Ebner
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=DKUGD3A91QKA.GJF8R0HPVWIJ@proxmox.com \
--to=l.sichert@proxmox.com \
--cc=c.ebner@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.