xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: AL13N <alien@rmail.be>
To: xen-devel@lists.xenproject.org
Subject: pci passthrough issue introduced between 4.14.1 and 4.15.0
Date: Tue, 01 Jun 2021 09:34:33 +0200	[thread overview]
Message-ID: <9562f5c0911567f12ed9fef8830f3018@mail.rmail.be> (raw)

Not 100% it's a bug or something i did wrong, but,

with xl create i start a PV with 3 pci passthroughs

after wards, xl pci-list shows all 3 nicely

looking at the domU boot logs, pcifront is only creating one pci device 
and lspci in the guest shows only 1 pci entry

in at least 4.14.1 it still works.

looking deeper, if you start with only 1 entry or 0 and you do 
pci-attach for the other pci entries, all of this works fine.

this is the pci section in question:

pci=['0000:04:00.0,permissive=1', 
'0000:00:1a.0,permissive=1,rdm_policy=relaxed,seize=1', 
'0000:00:1d.0,permissive=1,rdm_policy=relaxed,seize=1']

this works fine in 4.12.1 and 4.14.1, but fails in 4.15.0, however

booting with pci=['0000:04:00.0,permissive=1'] and then doing

[]# xl pci-attach <domain> 
'0000:00:1a.0,permissive=1,rdm_policy=relaxed,seize=1'
[]# xl pci-attach <domain> 
'0000:00:1d.0,permissive=1,rdm_policy=relaxed,seize=1'

also works,

Regards,

Maarten (alien on Libera and OFTC)



             reply	other threads:[~2021-06-01  7:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  7:34 AL13N [this message]
2021-06-01 10:03 ` pci passthrough issue introduced between 4.14.1 and 4.15.0 George Dunlap
2021-06-01  7:36 AL13N
2021-06-01 10:08 ` Jan Beulich
2021-06-01 14:06   ` AL13N
2021-06-01 14:28     ` AL13N
2021-06-01 14:33     ` Jan Beulich
2021-06-01 14:44       ` AL13N
2021-06-01 14:48         ` AL13N
2021-06-01 15:50           ` AL13N
2021-06-01 14:53         ` Jan Beulich
2021-06-03 16:01           ` AL13N
2021-06-04  6:56             ` Jan Beulich
2021-06-04  7:10               ` Juergen Gross
2021-06-04  8:37                 ` AL13N

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=9562f5c0911567f12ed9fef8830f3018@mail.rmail.be \
    --to=alien@rmail.be \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).