From: Malveeka Tewari <malveeka@gmail.com>
To: "Qiu, Michael" <michael.qiu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Error running dpdk app: cannot open /dev/uio
Date: Tue, 2 Dec 2014 17:41:18 -0800 [thread overview]
Message-ID: <CAFpzwwOEPJsjMLLiVbbAC7ef=UsXN5SBfadJnmrQBBc5=P8O_g@mail.gmail.com> (raw)
In-Reply-To: <533710CFB86FA344BFBF2D6802E60286C9C207@SHSMSX101.ccr.corp.intel.com>
Ohh ok .. thanks for the clarification :)
Malveeka
On Tue, Dec 2, 2014 at 5:36 PM, Qiu, Michael <michael.qiu@intel.com> wrote:
> On 12/3/2014 9:25 AM, Malveeka Tewari wrote:
> > I do have the uio and igb_uio modules loaded.
> > For my issue, I found a workaround by manually creating /dev/uio0
> > using mknod.
> > But I still get the vfio error.
> >
> > If I try "sudo modprobe vfio" but that gives an error that Module vfio
> > not found.
> > I tried looking for vfio.ko in the dpdk source tree as well but could
> > not find that module.
> > How can I install the vfio module?
>
> VFIO is supplied by kernel :)
> if you use uio then vfio can be ignored. It is just another way of
> things in new kernel(version > 3.6).
>
> Thanks,
> Michael
>
> >
> > Thanks!
> > Malveeka
> >
> >
> >
> > On Tue, Dec 2, 2014 at 5:12 PM, Qiu, Michael <michael.qiu@intel.com
> > <mailto:michael.qiu@intel.com>> wrote:
> >
> > Hi Malveeka,
> >
> > To be sure that you should have [uio, igb_uio] or [uio,
> > uio_pci_generic]
> > or [vfio] module loaded.
> >
> > Thanks,
> > Michael
> > On 12/3/2014 5:44 AM, Malveeka Tewari wrote:
> > > Hi
> > >
> > > I am trying to run the testpmd app as but I get the following
> > errors:
> > > EAL: VFIO could not be initialized
> > > EAL: Cannot open /dev/uio0: No such file or directory
> > > EAL: Error - exiting with code: 1
> > > Cause: Requested device 0000:07:00.0 cannot be used
> > >
> > > lsmod shows that the uio module is installed.
> > > Is there anything that's missing?
> > >
> > > Thanks!
> > > Malveeka
> > >
> > >
> > >
> > > Output on trying to run testpmd
> > >
> > > EAL: Detected 16 lcore(s)
> > > *EAL: cannot open VFIO container, error 2 (No such file or
> > directory)*
> > > *EAL: VFIO support could not be initialized*
> > > EAL: Setting up memory...
> > > EAL: Ask a virtual area of 0x200000 bytes
> > > EAL: Virtual area found at 0x7fe66ac00000 (size = 0x200000)
> > > EAL: Ask a virtual area of 0xffc00000 bytes
> > > EAL: Virtual area found at 0x7fe56ae00000 (size = 0xffc00000)
> > > EAL: Ask a virtual area of 0x200000 bytes
> > > EAL: Virtual area found at 0x7fe56aa00000 (size = 0x200000)
> > > EAL: Ask a virtual area of 0xfec00000 bytes
> > > EAL: Virtual area found at 0x7fe46bc00000 (size = 0xfec00000)
> > > EAL: Ask a virtual area of 0x400000 bytes
> > > EAL: Virtual area found at 0x7fe46b600000 (size = 0x400000)
> > > EAL: Ask a virtual area of 0x400000 bytes
> > > EAL: Virtual area found at 0x7fe46b000000 (size = 0x400000)
> > > EAL: Ask a virtual area of 0x400000 bytes
> > > EAL: Virtual area found at 0x7fe46aa00000 (size = 0x400000)
> > > EAL: Ask a virtual area of 0x400000 bytes
> > > EAL: Virtual area found at 0x7fe46a400000 (size = 0x400000)
> > > EAL: Ask a virtual area of 0x400000 bytes
> > > EAL: Virtual area found at 0x7fe469e00000 (size = 0x400000)
> > > EAL: Requesting 2048 pages of size 2MB from socket 0
> > > EAL: Requesting 2048 pages of size 2MB from socket 1
> > > EAL: TSC frequency is ~2266745 KHz
> > > EAL: Master core 3 is ready (tid=6cedb800)
> > > EAL: PCI device 0000:07:00.0 on NUMA socket -1
> > > EAL: probe driver: 8086:10fb rte_ixgbe_pmd
> > >
> > >
> > > *EAL: Cannot open /dev/uio0: No such file or directoryEAL: Error
> > - exiting
> > > with code: 1 Cause: Requested device 0000:07:00.0 cannot be used*
> > >
> >
> >
>
>
prev parent reply other threads:[~2014-12-03 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 21:43 Malveeka Tewari
2014-12-03 1:12 ` Qiu, Michael
2014-12-03 1:25 ` Malveeka Tewari
2014-12-03 1:36 ` Qiu, Michael
2014-12-03 1:41 ` Malveeka Tewari [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='CAFpzwwOEPJsjMLLiVbbAC7ef=UsXN5SBfadJnmrQBBc5=P8O_g@mail.gmail.com' \
--to=malveeka@gmail.com \
--cc=dev@dpdk.org \
--cc=michael.qiu@intel.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 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).