Hi Christophe,
Thanks a lot for the help. I tried reinstalling the VPP package and tried
the above steps the compilation worked successfully.
Unfortunately after running the VPP start service it did not start properly
I got an error with respect to "dpdk not enough free huge pages".
Could you please help and suggest if I am missing anything.
*Error Logs:*
---------------
[root@localhost vpp]# sudo service vpp start
Redirecting to /bin/systemctl start vpp.service
[root@localhost vpp]# sudo service vpp status -l
Redirecting to /bin/systemctl status -l vpp.service
● vpp.service - Vector Packet Processing Process
Loaded: loaded (/usr/lib/systemd/system/vpp.service; disabled; vendor
preset: disabled)
Active: inactive (dead)
Nov 24 08:02:54 localhost.localdomain vpp[28713]:
vlib_plugin_early_init:213: plugin path /usr/lib/vpp_plugins
Nov 24 08:02:54 localhost.localdomain vpp[28713]: load_one_plugin:92:
Loaded plugin: /usr/lib/vpp_plugins/ila_plugin.so
Nov 24 08:02:54 localhost.localdomain vpp[28713]: load_one_plugin:92:
Loaded plugin: /usr/lib/vpp_plugins/ioam_e2e_plugin.so
Nov 24 08:02:54 localhost.localdomain vpp[28713]: load_one_plugin:92:
Loaded plugin: /usr/lib/vpp_plugins/ioam_export_plugin.so
Nov 24 08:02:54 localhost.localdomain vpp[28713]: load_one_plugin:92:
Loaded plugin: /usr/lib/vpp_plugins/ioam_pot_plugin.so
Nov 24 08:02:54 localhost.localdomain vpp[28713]: load_one_plugin:92:
Loaded plugin: /usr/lib/vpp_plugins/ioam_trace_plugin.so
Nov 24 08:02:54 localhost.localdomain vpp[28713]: load_one_plugin:92:
Loaded plugin: /usr/lib/vpp_plugins/lb_plugin.so
Nov 24 08:02:54 localhost.localdomain vpp[28713]: load_one_plugin:92:
Loaded plugin: /usr/lib/vpp_plugins/libsixrd_plugin.so
Nov 24 08:02:54 localhost.localdomain vpp[28713]: load_one_plugin:92:
Loaded plugin: /usr/lib/vpp_plugins/snat_plugin.so
*Nov 24 08:02:54 localhost.localdomain vpp[28713]: vpp[28713]: dpdk_config:
not enough free huge pages[root@localhost vpp]#*
*Vpp startup config:*-----------------------------
unix {
nodaemon
log /tmp/vpp.log
full-coredump
}
dpdk {
uio-driver uio_pci_generic
}
api-trace {
on
}
api-segment {
gid vpp
}
"/etc/vpp/startup.conf" 18L, 144
Thanks & Regards,
Sreejith
On 24 November 2016 at 02:51, Christophe FONTAINE <
[email protected]> wrote:
> Hi,
>
>
>
> Did you installed all dependencies thru ‘make install-dep’ first ?
>
> On a fresh centos7 system / platform, I always do:
>
> - export PLATFORM=’<appropriate platform if required>’ (default
> is ‘vpp’)
>
> - make bootstrap
>
> - make install-dep
>
> - make pkg-rpm
>
>
>
> Christophe
>
>
>
>
>
> *From:* [email protected] [mailto:[email protected]] *On
> Behalf Of *Sreejith Surendran Nair
> *Sent:* jeudi 24 novembre 2016 07:10
> *To:* vpp-dev <[email protected]>
> *Subject:* [vpp-dev] VPP Compilation Issue on Centos
>
>
>
> Hi Team,
>
> I am using Centos 7 to build the VPP package but while running the vagrant
> build command I getting the below error with respect to Kernel headers ( no
> such file or directory).
>
> Could you please help and suggest if possible.
>
>
> [root@localhost 3.10.0-123.el7.x86_64]# uname -r
> 3.10.0-123.el7.x86_64
>
> Error:
> --------
> [root@localhost 3.10.0-123.el7.x86_64]# ./build-root/vagrant/build.sh
>
> == Build lib/librte_eal/linuxapp/eal
> == Build lib/librte_eal/linuxapp/igb_uio
> *make: *** /lib/modules/3.10.0-123.el7.x86_64/build: No such file or
> directory. Stop.*
> make[11]: *** [igb_uio.ko] Error 2
> make[10]: *** [igb_uio] Error 2
> make[10]: *** Waiting for unfinished jobs....
> CC eal.o
> CC eal_hugepage_info.o
> CC eal_memory.o
> CC eal_thread.o
> CC eal_log.o
> CC eal_vfio.o
> CC eal_vfio_mp_sync.o
> CC eal_pci.o
> CC eal_pci_uio.o
> CC eal_pci_vfio.o
> CC eal_debug.o
> CC eal_lcore.o
> CC eal_timer.o
> CC eal_interrupts.o
> CC eal_alarm.o
> CC eal_common_lcore.o
> CC eal_common_timer.o
> CC eal_common_memzone.o
> CC eal_common_log.o
> CC eal_common_launch.o
> CC eal_common_pci.o
> CC eal_common_pci_uio.o
> CC eal_common_memory.o
> CC eal_common_tailqs.o
> CC eal_common_cpuflags.o
> CC eal_common_errno.o
> CC eal_common_string_fns.o
> CC eal_common_hexdump.o
> CC eal_common_devargs.o
> CC eal_common_dev.o
> CC eal_common_options.o
> CC eal_common_thread.o
> CC eal_common_proc.o
> CC rte_malloc.o
> CC malloc_elem.o
> CC malloc_heap.o
> CC rte_keepalive.o
> CC rte_cpuflags.o
> CC rte_spinlock.o
> SYMLINK-FILE include/exec-env/rte_interrupts.h
> SYMLINK-FILE include/exec-env/rte_kni_common.h
> SYMLINK-FILE include/exec-env/rte_dom0_common.h
> AR librte_eal.a
> INSTALL-LIB librte_eal.a
> make[9]: *** [linuxapp] Error 2
> make[8]: *** [librte_eal] Error 2
> make[7]: *** [lib] Error 2
> make[6]: *** [all] Error 2
> make[5]: *** [pre_install] Error 2
> make[4]: *** [install] Error 2
> make[4]: Leaving directory `/home/techmahindra/source_
> vpp/vpp/build-root/build-vpp-native/dpdk/dpdk-16.07'
> make[3]: ***
> [/home/techmahindra/source_vpp/vpp/build-root/build-vpp-native/dpdk/.build.ok]
> Error 2
> make[3]: Leaving directory `/home/techmahindra/source_vpp/vpp/dpdk'
> make[2]: *** [dpdk-install] Error 2
> make[2]: Leaving directory `/home/techmahindra/source_vpp/vpp/build-root'
> make[1]: *** [install-rpm] Error 1
> make[1]: Leaving directory `/home/techmahindra/source_vpp/vpp/build-root'
> make: *** [pkg-rpm] Error 2
> [root@localhost vagrant]#
>
> Directory (checked manually):
> ------------------------------------------
> [root@localhost modules]# cd 3.10.0-123.el7.x86_64/
> [root@localhost 3.10.0-123.el7.x86_64]# ls
> build modules.alias.bin modules.dep modules.modesetting
> modules.symbols vdso
> extra modules.block modules.dep.bin modules.networking
> modules.symbols.bin
> kernel modules.builtin modules.devname modules.order
> source
> modules.alias modules.builtin.bin modules.drm modules.softdep
> updates
> [root@localhost 3.10.0-123.el7.x86_64]# cd build
> bash: cd: build: No such file or directory
>
>
>
> Thanks & Regards,
>
> Sreejith
>
> This message and any attachments (the "message") are confidential,
> intended solely for the addressees. If you are not the intended recipient,
> please notify the sender immediately by e-mail and delete this message from
> your system. In this case, you are not authorized to use, copy this message
> and/or disclose the content to any other person. E-mails are susceptible to
> alteration. Neither Qosmos nor any of its subsidiaries or affiliates shall
> be liable for the message if altered, changed or falsified.
>
> Ce message et toutes ses pièces jointes (ci-après le "message")sont
> confidentiels et établis à l'intention exclusive de ses destinataires. Si
> vous avez reçu ce message par erreur, merci d’en informer immédiatement son
> émetteur par courrier électronique et d’effacer ce message de votre
> système. Dans cette hypothèse, vous n’êtes pas autorisé à utiliser, copier
> ce message et/ou en divulguer le contenu à un tiers. Tout message
> électronique est susceptible d'altération. Qosmos et ses filiales déclinent
> toute responsabilité au titre de ce message s'il a été altéré, déformé ou
> falsifié.
>
_______________________________________________
vpp-dev mailing list
[email protected]
https://lists.fd.io/mailman/listinfo/vpp-dev
