From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: RanjithKumar <ranjithdvk@gmail.com>, "pxv3620@rit.edu" <pxv3620@rit.edu>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] FATAL: Module uio not found
Date: Thu, 14 Sep 2017 05:15:54 +0000 [thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E36512C8D3E@SHSMSX152.ccr.corp.intel.com> (raw)
In-Reply-To: <CACxh0QRgndgLsgFag38jX0U7zi+vHYqhQPmKqZuxPhUnGR2Ung@mail.gmail.com>
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of RanjithKumar
> Sent: Tuesday, September 12, 2017 8:31 PM
> To: pxv3620@rit.edu
> Cc: users
> Subject: Re: [dpdk-users] FATAL: Module uio not found
>
> Hello All,
>
> modprobe uio did not work , and below is the output VM NIC current drivers.
>
> ubuntu@mysite-vpgwu-slice1-25:~/dpdk-2.0.0/tools$ ./dpdk_nic_bind.py
> --status
>
> Network devices using DPDK-compatible driver
> ============================================
> <none>
>
> Network devices using kernel driver
> ===================================
> 0000:00:03.0 'Virtio network device' if= drv=virtio-pci unused=
> 0000:00:04.0 'Virtio network device' if= drv=virtio-pci unused=
> 0000:00:05.0 'Virtio network device' if= drv=virtio-pci unused=
> 0000:00:06.0 'Virtio network device' if= drv=virtio-pci unused=
> 0000:00:07.0 'Virtio network device' if= drv=virtio-pci unused=
>
> Other network devices
> =====================
> <none>
>
> So i followed below steps to use virtio-pci
>
>
> 1. modprobe vfio enable_unsafe_noiommu_mode=1
> 2. modprobe vfio-pci
> 3. ./dpdk_nic_bind.py -b vfio-pci 0000:00:04.0
>
> But i am getting below error while binding the Virtio NIC to DPDK
So far you cannot bind virtio devices with normal vfio-pci as the vIOMMU support is not upstreamed yet (https://patchwork.kernel.org/patch/9670273/).
Instead, you can bind virtio devices to vfio-pci (no-iommu mode). You can enable it like:
$ modprobe vfio enable_unsafe_noiommu_mode=1
$ modprobe vfio-pci
Thanks,
Jianfeng
>
> *Error: bind failed for 0000:00:04.0 - Cannot bind to driver vfio-pci
> Error: unbind failed for 0000:00:04.0 - Cannot open
> /sys/bus/pci/drivers//unbind*
>
> *Any input?*
>
> *Regards,*
> *Ranjith*
>
>
>
> Regards,
> Ranjith
>
>
> On Tue, Sep 12, 2017 at 2:31 PM, Pragash Vijayaragavan <pxv3620@rit.edu>
> wrote:
>
> > Hi,
> >
> > try modprobe igb_uio/ vfio-pci /uio_pci_generic
> >
> >
> >
> > Thanks,
> >
> > Pragash Vijayaragavan
> > Grad Student at Rochester Institute of Technology
> > email : pxv3620@rit.edu
> > ph : 585 764 4662 <(585)%20764-4662>
> >
> >
> > On Tue, Sep 12, 2017 at 4:54 AM, RanjithKumar <ranjithdvk@gmail.com>
> > wrote:
> >
> >> Hi All,
> >>
> >> I have installed DPDK in open stack lunched virtual machine and Modrobe
> is
> >> failing with below error
> >>
> >> modprobe: FATAL: Module uio not found
> >>
> >> Any input?
> >>
> >> Regards,
> >> Ranjith
> >>
> >
> >
prev parent reply other threads:[~2017-09-14 5:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACxh0QSc-56Tevr0Mfbxkq=TJTRKnL+_TS7EeKUKDfb7PhHW_Q@mail.gmail.com>
2017-09-12 9:01 ` Pragash Vijayaragavan
2017-09-12 12:31 ` RanjithKumar
2017-09-14 5:15 ` Tan, Jianfeng [this message]
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=ED26CBA2FAD1BF48A8719AEF02201E36512C8D3E@SHSMSX152.ccr.corp.intel.com \
--to=jianfeng.tan@intel.com \
--cc=pxv3620@rit.edu \
--cc=ranjithdvk@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).