From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Thierry Escande <thierry.escande@vates.tech>
Cc: xen-devel@lists.xenproject.org,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Juergen Gross" <jgross@suse.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [RFC PATCH v2 0/3] xl: Allow PCI devices to be passthrough'd via Qemu command line
Date: Fri, 10 Apr 2026 02:55:46 +0200 [thread overview]
Message-ID: <adhKlLvMB6PCRhwQ@mail-itl> (raw)
In-Reply-To: <20260409162000.1102680-1-thierry.escande@vates.tech>
[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]
On Thu, Apr 09, 2026 at 04:20:57PM +0000, Thierry Escande wrote:
> This series adds support for a new 'hotplug' option for PCI devices to be
> passthrough'd to guests.
>
> The current mechanism for device passthrough uses QMP device_add command
> to hot-plug PCI devices to the guest Qemu instance. This is an issue for
> guests running on Q35 chipset (preliminary support posted at [1]) since the
> Q35 PCI root bus does not support hotplug. Devices could be hotplugged to
> a secondary PCI bus but Xen only support 1 PCI bus for now.
>
> The 'hotplug' option allows to control how devices are attached to the
> guest, either by using the legacy QMP mechanism (this is the default) or by
> passing it directly to the Qemu command line using xen-pci-passthrough
> device.
>
> Example usage in cfg file:
> pci = [ "00:03.0,seize=1,hotplug=0" ]
>
> Since Qemu -device option accepts parameters in json format, this
> patchset adds a new internal function libxl__device_pci_get_qmp_json() that
> generates the device json object used for both QMP hotplug and command line
> passing.
> Also, the function libxl_pci_assignable() is made available from libxl.h
> for access in libxl_dm.c. I don't know if it's ok to make it public or if
> it should stay private. Maybe it should be renamed as
> libxl_device_pci_assignable() to match the other PCI device APIs.
>
> This has been successfully tested on Xen 4.22-dev and Qemu 10.0 running
> Debian VMs in both Bios and UEFI mode with a passthrough'd nvme disk.
> Disabling the hotplug mechanism might be made mandatory for Q35 machines
> later, once Q35 support is merged upstream.
>
> [1] https://lore.kernel.org/xen-devel/20260313163455.790692-1-thierry.escande@vates.tech/
I don't see relevant device option added to the QEMU cmdline:
https://gitlab.com/xen-project/people/marmarek/xen/-/jobs/13860278916
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-10 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 16:20 [RFC PATCH v2 0/3] xl: Allow PCI devices to be passthrough'd via Qemu command line Thierry Escande
2026-04-09 16:21 ` [RFC PATCH v2 1/3] xl: Add pci device hotplug option Thierry Escande
2026-04-09 16:21 ` [RFC PATCH v2 2/3] libxl: Allow PCI device passthrough using -device Qemu command line Thierry Escande
2026-04-09 16:21 ` [RFC PATCH v2 3/3] docs: provide description for pci hotplug option Thierry Escande
2026-04-10 0:55 ` Marek Marczykowski-Górecki [this message]
2026-04-10 8:16 ` [RFC PATCH v2 0/3] xl: Allow PCI devices to be passthrough'd via Qemu command line Thierry Escande
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=adhKlLvMB6PCRhwQ@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=anthony.perard@vates.tech \
--cc=berrange@redhat.com \
--cc=jgross@suse.com \
--cc=thierry.escande@vates.tech \
--cc=xen-devel@lists.xenproject.org \
/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.