From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH docs/guest-common/qemu-server v4 0/7] add new pci passthrough specific hookscript phase
Date: Wed, 26 Aug 2026 08:10:51 +0200 [thread overview]
Message-ID: <846b412b-eab9-47bf-a742-9d84a628da83@proxmox.com> (raw)
In-Reply-To: <20260825135502.3971930-1-d.csapak@proxmox.com>
On 8/25/26 3:54 PM, Dominik Csapak wrote:
> this series adds a new phase to the guest hookscript that is called for each
> passed throug pci device after it's prepared, but before the qemu process is
> started.
>
> See the last qemu-server commit for why that is interesting.
>
> changes from v4:
> * rebase on current master
> * fix `local %ENV` clearing the whole environment instead of
> just shadowing it, so the hookscript keeps the inherited environment
> * split the uuid handling out of the refactoring commit
> * call the hookscript once for both the mdev and the plain passthrough
> case instead of duplicating the call in both branches
> * add missing `use PVE::GuestHelpers;`
> * move the new phase before 'post-start' to match the actual call
> order, document that PVE_HOOK_MDEV_UUID is only set for mdevs, and
> mention what the phase is useful for
> * fix typos
>
> changes from v3:
> * split unrelated logic/refactoring changes out to their own patches
> * fix typos
>
not sure what i was thinking yesterday, of course these two
'changes from v3/v4' are both meant as 'changes from v3'
(i guess i started writing, paused, and finished later with
mindlessly adding a new section....)
> changes from v2:
> * rebase on current master
> * prefix hook script env variables with 'PVE_HOOK_'
>
>
> pve-guest-common:
>
> Dominik Csapak (1):
> helpers: exec hookscript: add optional parameters
>
> src/PVE/GuestHelpers.pm | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
>
> qemu-server:
>
> Dominik Csapak (5):
> pci: mdev preparation: always generate local uuid first
> pci: nvidia vgpu: correct wrong comment about uuid
> pci: factor 'prepare_pci_devices' out to PVE::QemuServer::PCI module
> pci: preparation: mdev: only generate uuid once
> pci: call hookscript for each prepared pci device
>
> src/PVE/QemuServer.pm | 45 ++++++---------------------------
> src/PVE/QemuServer/PCI.pm | 52 +++++++++++++++++++++++++++++++++++++++
> 2 files changed, 60 insertions(+), 37 deletions(-)
>
>
> pve-docs:
>
> Dominik Csapak (1):
> examples: add new hookscript phase to example hookscript
>
> examples/guest-example-hookscript.pl | 29 ++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
>
> Summary over all repositories:
> 4 files changed, 100 insertions(+), 38 deletions(-)
>
prev parent reply other threads:[~2026-08-26 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 13:54 [PATCH docs/guest-common/qemu-server v4 0/7] add new pci passthrough specific hookscript phase Dominik Csapak
2026-08-25 13:54 ` [PATCH guest-common v4 1/7] helpers: exec hookscript: add optional parameters Dominik Csapak
2026-08-25 13:54 ` [PATCH qemu-server v4 2/7] pci: mdev preparation: always generate local uuid first Dominik Csapak
2026-08-25 13:54 ` [PATCH qemu-server v4 3/7] pci: nvidia vgpu: correct wrong comment about uuid Dominik Csapak
2026-08-25 13:54 ` [PATCH qemu-server v4 4/7] pci: factor 'prepare_pci_devices' out to PVE::QemuServer::PCI module Dominik Csapak
2026-08-25 13:54 ` [PATCH qemu-server v4 5/7] pci: preparation: mdev: only generate uuid once Dominik Csapak
2026-08-25 13:54 ` [PATCH qemu-server v4 6/7] pci: call hookscript for each prepared pci device Dominik Csapak
2026-08-25 13:54 ` [PATCH docs v4 7/7] examples: add new hookscript phase to example hookscript Dominik Csapak
2026-08-26 6:10 ` Dominik Csapak [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=846b412b-eab9-47bf-a742-9d84a628da83@proxmox.com \
--to=d.csapak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox