From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Andriy Berestovskyy <aber@semihalf.com>,
raman geetha gopalakrishnan <glowingsun@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Reg VFIO-PCI Error
Date: Mon, 12 Sep 2016 15:55:17 +0100 [thread overview]
Message-ID: <fea44449-78e6-613a-5f9f-6cc80c512a78@intel.com> (raw)
In-Reply-To: <CAOysbxr7yttauasXxx+=-xK0nJ--9MoQ-mgUh3pUS6FwVxyyWA@mail.gmail.com>
Hi,
FYI vfio-pci is not supported inside a VM yet:
https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg04284.html
It is a work in progress (slide 19):
https://dpdksummit.com/Archive/pdf/2016USA/Day02-Session14-FranckBaudin-DPDKUSASummit2016.pdf
Regards,
Sergio
On 12/09/2016 14:51, Andriy Berestovskyy wrote:
> Hey Raman,
> Check dmesg for the details. I guess you have no IOMMU enabled, so you
> should either go ahead and enable it wit intel_iommu=on or use
> uio_pci_generic or igb_uio module instead of vfio-pci.
>
> Regards,
> Andriy
>
>
> On Mon, Sep 12, 2016 at 1:42 PM, raman geetha gopalakrishnan
> <glowingsun@gmail.com> wrote:
>> Hi DPDK-USERS,
>>
>> 1. I have installed DPDK on my virtual-box which runs ubuntu 16.04.1
>> (xenial).
>> 2. My DPDK version is 16.07
>> 3. When i try to bind ethernet device to VFIO module i get the following
>> error
>>
>> Error: bind failed for 0000:00:08.0 - cannot bind to driver vfio-pci [
>> this is for NIC 82545EM]
>> debug message gave the rrror
>> vfio-pci: probe of 0000:00:08.0 failed with error -22
>>
>>
>> Please Advice.
>>
>> Thanks
>> Raman
>
>
next prev parent reply other threads:[~2016-09-12 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 11:42 raman geetha gopalakrishnan
2016-09-12 13:51 ` Andriy Berestovskyy
2016-09-12 14:55 ` Sergio Gonzalez Monroy [this message]
2016-09-13 6:28 ` raman geetha gopalakrishnan
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=fea44449-78e6-613a-5f9f-6cc80c512a78@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=aber@semihalf.com \
--cc=glowingsun@gmail.com \
--cc=users@dpdk.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).