Wait, now if I try with uio_pci_generic.ko, I do not have to install dpdk.
One thing that is terribly confusing is that sometimes uio_pci_generic
shows up as the driver when I do vppctl show pci, and other times it is
just blank. Anyway, indeed there is no need to install dpdk or libdpdk0,
but on the other hand, I am having to manually modprobe uio_pci_generic,
and there is that issue of it appearing or not appearing when it desires in
the vppctl show pci results.

Burt

On Sun, Apr 9, 2017 at 2:46 PM, Burt Silverman <bur...@gmail.com> wrote:

> Hi John,
>
> I am pretty confused, too: I do not see igb_uio.ko in the vpp-plugins
> package, or anywhere else in VPP world. So I must install DPDK from Ubuntu,
> too, I guess. This is the first time I am trying to go beyond the build
> stage on this particular platform, and I have not had any luck so far
> getting my VirtualBox provided 82545EM adapter recognized in a useful way.
> Thank you if you can confirm.
>
> Burt
>
> On Sat, Apr 8, 2017 at 6:10 PM, John Lo (loj) <l...@cisco.com> wrote:
>
>> With 17.04/17.07, DPDK is moved to plugin and thus reside in vpp-plugin.
>> Thus, vpp-dpdk-dkms is obsolete and should be removed.  -John
>>
>>
>>
>> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
>> Behalf Of *Srikanth Vavilapalli
>> *Sent:* Saturday, April 08, 2017 3:01 PM
>> *To:* vpp-dev@lists.fd.io
>> *Subject:* [vpp-dev] Unable to install vpp 17.04 on ubuntu 16.04
>>
>>
>>
>> Hi
>>
>>
>>
>> I tried to install VPP version 17.04 on a Ubuntu 16.04 server and even
>> though installation was successful, the service status reports “Inactive”
>> with some core-dump (output below). Can anyone point me if I am missing
>> anything here? Appreciate your help.
>>
>>
>>
>> PS: I was able to install VPP 17.01 or VPP latest master (17.07) on this
>> same machine, but for some reasons, OpenDaylight-groupbasedpolicy was
>> reporting some errors with these two versions (With 17.01, I see errors
>> “Unknown augmentation node detected” and with 17.07, errors like “Node cs02
>> does not contain all capabilities required by vpp-renderer”)
>>
>>
>>
>>
>>
>>
>>
>> ericsson@cs02:~/all-in-one/vpp-binaries$ sudo bash install-vpp.sh
>>
>> Installing VPP...
>>
>> W: The repository 'https://nexus.fd.io/content/r
>> epositories/fd.io.stable.1704.ubuntu.xenial.main ./ Release' is not
>> signed.
>>
>> ….
>>
>> WARNING: The following packages cannot be authenticated!
>>
>>   vpp-lib vpp vpp-dev vpp-dpdk-dkms vpp-plugins
>>
>> Authentication warning overridden.
>>
>> Get:1 https://nexus.fd.io/content/repositories/fd.io.stable.1704.
>> ubuntu.xenial.main ./ vpp-lib 17.04-rc1~23-gb970bb7~b23 [1,572 kB]
>>
>> Get:2 https://nexus.fd.io/content/repositories/fd.io.stable.1704.
>> ubuntu.xenial.main ./ vpp 17.04-rc1~23-gb970bb7~b23 [261 kB]
>>
>> Get:3 https://nexus.fd.io/content/repositories/fd.io.stable.1704.
>> ubuntu.xenial.main ./ vpp-dev 17.04-rc1~23-gb970bb7~b23 [432 kB]
>>
>> Get:4 https://nexus.fd.io/content/repositories/fd.io.stable.1704.
>> ubuntu.xenial.main ./ vpp-dpdk-dkms 17.02-vpp2 [7,816 B]
>>
>> Get:5 https://nexus.fd.io/content/repositories/fd.io.stable.1704.
>> ubuntu.xenial.main ./ vpp-plugins 17.04-rc1~23-gb970bb7~b23 [1,359 kB]
>>
>> Fetched 3,632 kB in 2s (1,539 kB/s)
>>
>> Selecting previously unselected package vpp-lib.
>>
>> …
>>
>> DKMS: install completed.
>>
>> Building initial module for 4.4.0-72-generic
>>
>> Done.
>>
>>
>>
>> igb_uio:
>>
>> Running module version sanity check.
>>
>> - Original module
>>
>>    - No original module exists within this kernel
>>
>> - Installation
>>
>>    - Installing to /lib/modules/4.4.0-72-generic/updates/dkms/
>>
>>
>>
>> depmod....
>>
>>
>>
>> DKMS: install completed.
>>
>> Setting up vpp-plugins (17.04-rc1~23-gb970bb7~b23) ...
>>
>> Processing triggers for libc-bin (2.23-0ubuntu7) ...
>>
>> Installing VPP done.
>>
>>
>>
>> ericsson@cs02:~/all-in-one/vpp-binaries$ sudo service vpp status
>>
>> ● vpp.service - vector packet processing engine
>>
>>    Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor
>> preset: enabled)
>>
>>    Active: inactive (dead) (Result: core-dump) since Sat 2017-04-08
>> 11:44:01 PDT; 31s ago
>>
>>   Process: 63210 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm
>> /dev/shm/vpe-api (code=exited, status=0/SUCCESS)
>>
>>   Process: 62983 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf
>> (code=dumped, signal=ABRT)
>>
>>   Process: 62977 ExecStartPre=/sbin/modprobe uio_pci_generic
>> (code=exited, status=0/SUCCESS)
>>
>>   Process: 62966 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm
>> /dev/shm/vpe-api (code=exited, status=0/SUCCESS)
>>
>> Main PID: 62983 (code=dumped, signal=ABRT)
>>
>>
>>
>> Apr 08 11:44:00 cs02 systemd[1]: vpp.service: Unit entered failed state.
>>
>> Apr 08 11:44:00 cs02 systemd[1]: vpp.service: Failed with result
>> 'core-dump'.
>>
>> Apr 08 11:44:01 cs02 systemd[1]: vpp.service: Service hold-off time over,
>> scheduling restart.
>>
>> Apr 08 11:44:01 cs02 systemd[1]: Stopped vector packet processing engine.
>>
>> Apr 08 11:44:01 cs02 systemd[1]: vpp.service: Start request repeated too
>> quickly.
>>
>> Apr 08 11:44:01 cs02 systemd[1]: Failed to start vector packet processing
>> engine.
>>
>> ericsson@cs02:~/all-in-one/vpp-binaries$
>>
>>
>>
>>
>>
>> Thanks
>>
>> Srikanth
>>
>> _______________________________________________
>> vpp-dev mailing list
>> vpp-dev@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/vpp-dev
>>
>
>
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to