From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Ferdinand Nölscher" <ferdinand@outlook.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>, xen-devel@lists.xen.org
Subject: Re: AMD IOMMU disabled - No Perdev Intremap
Date: Sun, 6 Oct 2013 13:58:38 +0100 [thread overview]
Message-ID: <52515E7E.8050209@citrix.com> (raw)
In-Reply-To: <BLU0-SMTP117FEB145605B4ED60300D4A5120@phx.gbl>
On 06/10/2013 13:56, Ferdinand Nölscher wrote:
> Hi Sander,
>
> Thanks for your reply.
>
> On 10/06/2013 02:10 PM, Sander Eikelenboom wrote:
>> Sunday, October 6, 2013, 1:36:33 PM, you wrote:
>>
>>> Hi!
>>>> From other people posting to this list, I know that there has
>>>> been a
>>> bug related to the issue described in Xen Security Advisory 36
>>> that disables iommu for some AMD users like me.
>> What motherboard do you have ?
> I have an ASUS M5A99X EVO Rev 1.01
>
>
>> It depends if it's the north or southbridge ioapic but try using
>> the new xen boot parameter: (add it to the xen.gz line in grub)
>>
>> ivrs_ioapic[0]=00:14.0
>>
>> or
>>
>> ivrs_ioapic[0]=00:00.1
> I tried both, it still fails to enable i/o virtualisation.
Can you post a full xl dmesg, booting with iommu=debug,verbose as well?
~Andrew
next prev parent reply other threads:[~2013-10-06 12:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 11:36 AMD IOMMU disabled - No Perdev Intremap Ferdinand Nölscher
2013-10-06 12:10 ` Sander Eikelenboom
2013-10-06 12:56 ` Ferdinand Nölscher
2013-10-06 12:58 ` Andrew Cooper [this message]
2013-10-06 13:09 ` Ferdinand Nölscher
2013-10-06 14:38 ` Sander Eikelenboom
2013-10-06 14:45 ` Andrew Cooper
2013-10-06 14:59 ` Sander Eikelenboom
2013-10-06 17:28 ` Ferdinand Nölscher
2013-10-06 17:45 ` Sander Eikelenboom
2013-10-06 17:57 ` Ferdinand Nölscher
2013-10-06 18:03 ` Sander Eikelenboom
2013-10-08 16:39 ` Ferdinand Nölscher
2013-10-08 16:44 ` Sander Eikelenboom
2013-10-07 7:33 ` Jan Beulich
2013-10-06 14:40 ` Andrew Cooper
2013-10-06 18:14 ` Ferdinand Nölscher
2013-10-08 0:08 ` Suravee Suthikulpanit
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=52515E7E.8050209@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ferdinand@outlook.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.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).