From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>,
Lukas Sichert <l.sichert@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH v3 pve-qemu qemu-server 0/6] bypass host page cache for restore on zvol
Date: Thu, 20 Aug 2026 14:07:51 +0200 [thread overview]
Message-ID: <8a1e0166-f721-4832-a4ec-b71663c60b35@proxmox.com> (raw)
In-Reply-To: <DKTOJDG9FQ00.31RUAI1TR35Y2@proxmox.com>
On 20/08/2026 11:56, Lukas Sichert wrote:
> On 2026-08-20 11:05, Christian Ebner <c.ebner@proxmox.com> wrote:
>
>> This patch series skips writing to the host page cache for restores
>> to zvols, with the intention to avoid potential I/O delay issues for
>> other ZFS-backed VMs during page writeback on certain setups, as
>> reported in enterprise support and reproduced internally.
>>
>> This patch series adds an optional no-cache parameter for pbs-restore
>> command invocation, setting the BDRV_O_NOCACHE flag for the block
>> device being restored to and sets `cache=none` for vma restores.
>
> When I test patched debs on my testmachines I normally bump the version
> with a local<x> suffigx. package_name_1.2.3 is deployed as
> package_name_1.2.3+local1. When starting a restore with this and v2, I got
> the error 'TASK ERROR: internal error: cannot check version of invalid
> string 'unknown' at /usr/share/perl5/PVE/QemuServer/Helpers.pm line 104.'
>
> Christian proposed the following diff off-list, which worked for me.
>
> diff --git a/src/PVE/QemuServer/Helpers.pm b/src/PVE/QemuServer/Helpers.pm
> index 5065a457..1ed48a3b 100644
> --- a/src/PVE/QemuServer/Helpers.pm
> +++ b/src/PVE/QemuServer/Helpers.pm
> @@ -68,7 +68,7 @@ sub kvm_user_version {
> $kvm_mtime->{$binary} = $st->mtime;
>
> my $binary_version_re = qr/(\d+\.\d+(\.\d+)?)(\.\d+)?/;
> - my $package_version_re = qr/\(pve-qemu-kvm_(\d+\.\d+(\.\d+)?-\d+)\)/;
> + my $package_version_re = qr/\(pve-qemu-kvm_(\d+\.\d+(\.\d+)?-\d+)(\+[a-zA-Z0-9]+)?\)/;
>
> my $code = sub {
> my $line = shift;
>
> I wouldn't consider this a blocker, but it would be a nice to have in a
> potential next version.
meh, that's far from great - re-implementing all off debians
package version seems also futile and hard to maintain; so either
we use "dpkg --compare-versions ..." directly via run_command or
just bump the versioned dependency in d/control here - even though
the latter makes downgrading slightly more work, it is IMO still more
preferable for this here, and it would allow us to drop like three
patches FWICT.
next prev parent reply other threads:[~2026-08-20 12:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 9:05 [PATCH v3 pve-qemu qemu-server 0/6] bypass host page cache for restore on zvol Christian Ebner
2026-08-20 9:05 ` [PATCH v3 pve-qemu 1/1] pbs-restore: add optional no-cache flag to bypass host page cache Christian Ebner
2026-08-20 9:05 ` [PATCH v3 qemu-server 2/6] helpers: never cache `unknown` on failed kvm binary version check Christian Ebner
2026-08-20 9:05 ` [PATCH v3 qemu-server 3/6] helpers: optionally get package version for kvm_user_version() Christian Ebner
2026-08-20 9:05 ` [PATCH v3 qemu-server 4/6] helpers: add helper for min kvm package version comparison Christian Ebner
2026-08-20 9:05 ` [PATCH v3 qemu-server 5/6] pbs-restore: set 'no-cache' on block devices backed by zfspool Christian Ebner
2026-08-20 9:05 ` [PATCH v3 qemu-server 6/6] vma restore: skip page cache " Christian Ebner
2026-08-20 9:56 ` [PATCH v3 pve-qemu qemu-server 0/6] bypass host page cache for restore on zvol Lukas Sichert
2026-08-20 12:07 ` Thomas Lamprecht [this message]
2026-08-20 12:36 ` Christian Ebner
2026-08-20 11:36 ` Lukas Sichert
2026-08-20 13:12 ` 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=8a1e0166-f721-4832-a4ec-b71663c60b35@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=l.sichert@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.