From: William Tu <u9012063@gmail.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Nishank Trivedi <nishank.trivedi@netapp.com>, kvm@vger.kernel.org
Subject: Re: pci passthrough error about insufficient iommu width
Date: Wed, 6 Aug 2014 14:49:39 -0700 [thread overview]
Message-ID: <CALDO+SaiWDw36pP8i0aaK50kPathQiBuxNuy_ALWw0Cq=1+oSQ@mail.gmail.com> (raw)
In-Reply-To: <1407360689.316.182.camel@ul30vt.home>
I encountered the same "IOMMU width is not sufficient" issue. Using
VFIO works ok for me.
On Wed, Aug 6, 2014 at 2:31 PM, Alex Williamson
<alex.williamson@redhat.com> wrote:
> On Wed, 2014-08-06 at 14:22 -0700, Nishank Trivedi wrote:
>> Hi
>>
>> I'm trying to do a pci-passthrough of Intel 82599 10GbE card, with guest
>> having 8G of memory. I see following error -
>>
>> intel_iommu_map: iommu width (48) is not sufficient for the mapped
>> address (fffffffffe001000)
>> kvm_iommu_map_address:iommu failed to map pfn=45800
>>
>> I checked IOMMU capability register and SAGAW as well as MGAW are 48bits
>> for both IOMMU.
>>
>> # dmesg | grep ecap
>> dmar: IOMMU 0: reg_base_addr dfff0000 ver 1:0 cap d2078c106f0462 ecap f020fe
>> dmar: IOMMU 1: reg_base_addr bfff0000 ver 1:0 cap d2078c106f0462 ecap f020fe
>>
>> # cat /proc/cpuinfo | grep "address sizes"
>> address sizes : 46 bits physical, 48 bits virtual
>>
>> In DMAR table, I see host address width set to "2D", i.e. 46bit, which
>> is ok as it is same as physical address size. Any suggestions on what
>> might be going wrong here?
>
> Try vfio-pci instead of pci-assign
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-08-06 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 21:22 pci passthrough error about insufficient iommu width Nishank Trivedi
2014-08-06 21:31 ` Alex Williamson
2014-08-06 21:49 ` William Tu [this message]
2014-08-07 6:12 ` Nishank Trivedi
2014-08-07 15:02 ` Alex Williamson
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='CALDO+SaiWDw36pP8i0aaK50kPathQiBuxNuy_ALWw0Cq=1+oSQ@mail.gmail.com' \
--to=u9012063@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nishank.trivedi@netapp.com \
/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.