Shmuel, When I run that command I got the following:
$ sudo dpdk-testpmd EAL: Detected 1 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'PA' EAL: No available hugepages reported in hugepages-32768kB EAL: No available hugepages reported in hugepages-64kB EAL: No available hugepages reported in hugepages-1048576kB EAL: Probing VFIO support... EAL: PCI device 0008:00:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt EAL: PCI device 0008:01:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt EAL: PCI device 0008:01:00.1 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt EAL: PCI device 0008:01:00.2 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt EAL: PCI device 0008:01:00.3 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt testpmd: No probed ethernet devices EAL: Error - exiting with code: 1 Cause: No cores defined for forwarding Check the core mask argument I set all the hugepages it was complaining about to 4 and 1024 pages, unmounted and remounted /mnt/huge and reran the command: $ sudo dpdk-testpmd EAL: Detected 1 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'PA' EAL: 4 hugepages of size 33554432 reserved, but no mounted hugetlbfs found for that size EAL: 1024 hugepages of size 65536 reserved, but no mounted hugetlbfs found for that size EAL: 4 hugepages of size 1073741824 reserved, but no mounted hugetlbfs found for that size EAL: Probing VFIO support... EAL: PCI device 0008:00:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt EAL: PCI device 0008:01:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt EAL: PCI device 0008:01:00.1 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt EAL: PCI device 0008:01:00.2 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt EAL: PCI device 0008:01:00.3 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 14e4:16f0 net_bnxt testpmd: No probed ethernet devices EAL: Error - exiting with code: 1 Cause: No cores defined for forwarding Check the core mask argument Re-starting the vpp service I get the same error: /usr/bin/vpp[7774]: dpdk: EAL init args: -c 1 -n 4 --in-memory --huge-dir /mnt/huge --file-prefix sst100 -w 0008:01:00.0 --master-lcore 0 vpp[7774]: EAL: FATAL: Cannot get hugepage information. vpp[7774]: vpp[7774]: dpdk_config: rte_eal_init returned -1 ________________________________ From: Shmuel H <s...@tkos.co.il> Sent: Tuesday, May 26, 2020 3:03 PM To: Manoj Iyer <manoj.i...@arm.com>; vpp-dev@lists.fd.io <vpp-dev@lists.fd.io>; bga...@cisco.com <bga...@cisco.com> Cc: Rodney Schmidt <rodney.schm...@arm.com>; Kshitij Sudan <kshitij.su...@arm.com> Subject: Re: [vpp-dev] VPP fails to start - error message EAL: FATAL: Cannot get hugepage information. Strange. I usually unmount and then mount the hugepages mount point before using it, just to be sure. Maybe the two different mount points confuse DPDK somehow. By the way, if you have dpdk-testpmd, what is its output? Does it return the same error message? - Shmuel Hazan mailto:s...@tkos.co.il | tel:+972-523-746-435 | http://tkos.co.il On 26 May 2020 20:57:30 "Manoj Iyer" <manoj.i...@arm.com> wrote: ________________________________ From: Benoit Ganne (bganne) <bga...@cisco.com> Sent: Tuesday, May 26, 2020 12:31 PM To: Manoj Iyer <manoj.i...@arm.com>; vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> Cc: Rodney Schmidt <rodney.schm...@arm.com>; Kshitij Sudan <kshitij.su...@arm.com> Subject: RE: [vpp-dev] VPP fails to start - error message EAL: FATAL: Cannot get hugepage information. > I removed the plugin and it starts the service! [...] > At this point, I think I should be able to use the VPP console to set up > the interfaces etc. Is there any other gotcha I need to be aware of ? Which interfaces are you going to use to rx/tx packets? VPP natively supports some Intel, Mellanox and virtual NICs but otherwise you'll need to use DPDK. And for that you'll need the DPDK plugin. That is exactly the problem now. I need to use DPDK, and how do I get the plugin to work? Do we know the root cause of the issue why the plugin fails? Any pointers on this would be really appreciated. Thanks Manoj Iyer IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16510): https://lists.fd.io/g/vpp-dev/message/16510 Mute This Topic: https://lists.fd.io/mt/74481192/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
