All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Dingwall <james-xen@dingwall.me.uk>
To: xen-devel@lists.xenproject.org
Subject: xen 4.8.2 iommu=off problems
Date: Tue, 5 Dec 2017 10:23:01 +0000	[thread overview]
Message-ID: <20171205102301.GA123715@dingwall.me.uk> (raw)

Hi,

We have 3x HPE DL180 Gen9 servers, one of these is dual CPU the others single.  They are all running the same 
xen 4.8.2 build (plus some XSA patches) and Linux 4.1.46 dom0/guest kernel.  On the single CPU systems we can 
successfully passthrough ports from the onboard controller (igb) and additional PCIe card when iommu=off 
x2apic=off (vs iommu=on), on the dual cpu system the onboard interfaces appear but on passthrough to the driver 
domain the kernel continually logs "igb 0000:05:00.0 eth0: Reset adapter" messages for both interfaces and they 
cannot be used.

I have compared firmware/BIOS versions on all the systems and found them to be identical (although not 
necessarily latest).  Previously all the systems ran xen 4.4.3 + Linux 4.1.43 without any passthrough problems 
and iommu=off.

The combination of iommu=off and x2apic=on does not work as xen panics that it "Couldn't enable IOMMU" (I think 
from xen/drivers/passthrough/iommu.c).  The reason for using iommu=off is that we have noted a performance drop 
in HVM guests for iommu=on.

I'm looking for some suggestions on how to proceed in order to get the dual cpu system working again with 
iommu=off.

Thanks,
James

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

                 reply	other threads:[~2017-12-05 10:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20171205102301.GA123715@dingwall.me.uk \
    --to=james-xen@dingwall.me.uk \
    --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.