From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs/guest-common/qemu-server 0/3] add new pci passthrough specific hookscript phase
Date: Wed, 14 Jan 2026 16:50:29 +0100 [thread overview]
Message-ID: <20260114155043.3313473-1-d.csapak@proxmox.com> (raw)
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 qemu-server commit for why that is interesting.
pve-guest-common:
Dominik Csapak (1):
helpers: exec hookscript: add optional parameters
src/PVE/GuestHelpers.pm | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
qemu-server:
Dominik Csapak (1):
pci: call hookscript for each prepared pci device
src/PVE/QemuServer.pm | 18 +++++++++++++++---
src/PVE/QemuServer/PCI.pm | 1 +
2 files changed, 16 insertions(+), 3 deletions(-)
pve-docs:
Dominik Csapak (1):
examples: add new hookscript phase to example hookscript
examples/guest-example-hookscript.pl | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
Summary over all repositories:
4 files changed, 43 insertions(+), 5 deletions(-)
--
Generated by git-murpp 0.8.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2026-01-14 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 15:50 Dominik Csapak [this message]
2026-01-14 15:50 ` [pve-devel] [PATCH guest-common 1/1] helpers: exec hookscript: add optional parameters Dominik Csapak
2026-01-14 15:50 ` [pve-devel] [PATCH qemu-server 1/1] pci: call hookscript for each prepared pci device Dominik Csapak
2026-01-14 15:50 ` [pve-devel] [PATCH docs 1/1] examples: add new hookscript phase to example hookscript Dominik Csapak
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=20260114155043.3313473-1-d.csapak@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