From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
Subject: applied: [PATCH docs/guest-common/qemu-server v5 0/9] add new pci passthrough specific hookscript phase
Date: Tue, 3 Nov 2026 00:07:57 +0100 [thread overview]
Message-ID: <179366086199.2082684.2094502620301393424.b4-ty@b4> (raw)
In-Reply-To: <20260923070522.434715-1-d.csapak@proxmox.com>
On Wed, 23 Sep 2026 09:04:53 +0200, 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:
> * fixed code style
> * improved comment for ENV copying
> * added cleanup commit for renaming variable
> * added commit to downgrade to warn for unknown phases in example hookscript
>
> [...]
Applied, thanks!
[docs] applied to git/pve-docs.git (master)
[1/2] examples: add new hookscript phase to example hookscript
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=215dd29622a8628ed72b572335f7da750aa7b4c1
[2/2] examples: downgrade 'die' in example hookscript to 'warn'
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=c5329d73b8b544d637442608339e91789afacadb
[guest-common] applied to pve-guest-common.git (master)
[1/1] helpers: exec hookscript: add optional parameters
https://git.proxmox.com/?p=pve-guest-common.git;a=commitdiff;h=f1a9a87915b6c66b07010b8041a387e497dff712
[qemu-server] applied to qemu-server.git (master)
[1/6] pci: mdev preparation: always generate local uuid first
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=9e62daafbee64bf2c352bcea6799d01cae1a0912
[2/6] pci: nvidia vgpu: correct wrong comment about uuid
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=6f710823dc2bf339ee6eb636218ff1e4fb3d4f1d
[3/6] pci: factor 'prepare_pci_devices' out to PVE::QemuServer::PCI module
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=f3e741ada57340a3c489d8ec9c3cbe86b71d726c
[4/6] code cleanup: pci: rename 'd' variable to 'pci_device'
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=75d37016acb8d134baeddd5504cc62880618c1ae
[5/6] pci: preparation: mdev: only generate uuid once
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=37bdfbbd0c493ef059582b69ba8cfe631744b536
[6/6] pci: call hookscript for each prepared pci device
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=6cd6e846ba9bcd00892ed5af415ba9178b036dd9
prev parent reply other threads:[~2026-11-02 23:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 7:04 [PATCH docs/guest-common/qemu-server v5 0/9] add new pci passthrough specific hookscript phase Dominik Csapak
2026-09-23 7:04 ` [PATCH guest-common v5 1/9] helpers: exec hookscript: add optional parameters Dominik Csapak
2026-09-23 7:04 ` [PATCH qemu-server v5 2/9] pci: mdev preparation: always generate local uuid first Dominik Csapak
2026-09-23 7:04 ` [PATCH qemu-server v5 3/9] pci: nvidia vgpu: correct wrong comment about uuid Dominik Csapak
2026-09-23 7:04 ` [PATCH qemu-server v5 4/9] pci: factor 'prepare_pci_devices' out to PVE::QemuServer::PCI module Dominik Csapak
2026-09-23 7:04 ` [PATCH qemu-server v5 5/9] code cleanup: pci: rename 'd' variable to 'pci_device' Dominik Csapak
2026-09-23 7:04 ` [PATCH qemu-server v5 6/9] pci: preparation: mdev: only generate uuid once Dominik Csapak
2026-09-23 7:05 ` [PATCH qemu-server v5 7/9] pci: call hookscript for each prepared pci device Dominik Csapak
2026-09-23 7:05 ` [PATCH docs v5 8/9] examples: add new hookscript phase to example hookscript Dominik Csapak
2026-09-23 7:05 ` [PATCH docs v5 9/9] examples: downgrade 'die' in example hookscript to 'warn' Dominik Csapak
2026-10-02 13:39 ` [PATCH docs/guest-common/qemu-server v5 0/9] add new pci passthrough specific hookscript phase Elias Huhsovitz
2026-11-02 23:07 ` Thomas Lamprecht [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=179366086199.2082684.2094502620301393424.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=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