From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Problem with PCI-passthrough to PV guest
Date: Wed, 6 May 2026 11:18:28 +0200 [thread overview]
Message-ID: <afsHZMH1oVpds-wg@macbook.local> (raw)
In-Reply-To: <4ca0f24d-2526-4e49-a4e0-f8497aa8f4b0@suse.com>
On Wed, May 06, 2026 at 10:45:49AM +0200, Jürgen Groß wrote:
> On 05.05.26 20:47, Roger Pau Monné wrote:
> > On Tue, May 05, 2026 at 05:53:31PM +0200, Jürgen Groß wrote:
> > > SUSE QA is seeing a problem with PCI-passthrough of a SR-IOV to a PV guest
> > > running a 6.4 based kernel, but I can reproduce the problem with upstream
> > > kernel, too.
>
> Uh, seems my tested kernel was only "nearly upstream" (it was an early
> 7.0 kernel). It was missing commit 0949c646d646, which makes the difference.
>
> So for now this issue will only show up for cases where a PV-guest is
> setup for PCI passthrough and it gets memory hotplugged before the PCI
> device is added to it.
Hm, yes, this is yet more fallout from the unpopulated-alloc changes.
For PV guests that have the e820 host available we could try to create
the hotplug regions over what are host RAM region in the memory map,
as then we know we won't be overlapping with MMIO areas.
Thanks, Roger.
next prev parent reply other threads:[~2026-05-06 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 15:53 Problem with PCI-passthrough to PV guest Jürgen Groß
2026-05-05 18:47 ` Roger Pau Monné
2026-05-06 8:45 ` Jürgen Groß
2026-05-06 9:18 ` Roger Pau Monné [this message]
2026-05-06 11:15 ` Marek Marczykowski-Górecki
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=afsHZMH1oVpds-wg@macbook.local \
--to=roger.pau@citrix.com \
--cc=jgross@suse.com \
--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.