I am trying to set up VPP on a server running stream 2026.03 using a Intel E810 2x100 NIC
The commit is not working and when trying to run vpp binary with the config generated by commit it shows some memory error.
Result
Config and commit
admin@vyos# set vpp settings interface eth5
[edit]
admin@vyos# set vpp settings interface eth6
[edit]
admin@vyos# commit
[ vpp ]
WARNING: NOTE: Current dataplane capacity (estimated): 2.1 M IPv4
routes. Exceeding these values will lead to a dataplane out-of-memory
condition and a crash. Extensive use of features like ACLs, NAT and
others may reduce the numbers above. Please read the documentation for
details: https://docs.vyos.io/
An error occurred: VPP service is not running or failed to start. VPP
service will be restarted with the previous configuration
[[vpp]] failed
Commit failed
Traceback (most recent call last):
File “/usr/libexec/vyos/reset_section.py”, line 104, in
wait_for_commit_lock()
File “/usr/lib/python3/dist-packages/vyos/utils/commit.py”, line 59, in wait_for_commit_lock
while commit_in_progress():
^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/vyos/utils/commit.py”, line 39, in commit_in_progress
raise OSError(‘This functions needs to be run as root to return correct results!’)
OSError: This functions needs to be run as root to return correct results!
[edit]
Running VPP-binary with generated config
admin@vyos# sudo /usr/bin/vpp -c /run/vpp/vpp.conf
vpp[5923]: clib_sysfs_prealloc_hugepages:236: pre-allocating 8 additional 2048K hugepages on numa node 0
set_mempolicy: Invalid argument
.
.
Repeated 1200 times
.
.
set_mempolicy: Invalid argument
vpp[5923]: received signal SIGSEGV, PC 0x7f5130ddb00b, faulting address 0x28
vpp[5923]: Code: 0f b7 70 28 48 89 df e8 b9 6a 01 00 85 c0 0f 85 c4 01 00 00
vpp[5923]: #0 0x00007f5130ddb00b
vpp[5923]: from /usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so
vpp[5923]: #1 0x00007f5130de5ffa
vpp[5923]: from /usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so
vpp[5923]: #2 0x00007f5130dcc3a5
vpp[5923]: from /usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so
vpp[5923]: #3 0x00007f5130dcb9bc
vpp[5923]: from /usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so
vpp[5923]: #4 0x00007f513077f322
vpp[5923]: from /usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so
vpp[5923]: #5 0x00007f513077e923
vpp[5923]: from /usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so
vpp[5923]: #6 0x00007f5130971934
vpp[5923]: from /usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so
vpp[5923]: #7 0x00007f5130999a5a
vpp[5923]: from /usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so
vpp[5923]: #8 0x00007f5131543103 clib_sysfs_read_bitmap + 0x16fe3
vpp[5923]: from /usr/lib/x86_64-linux-gnu/vpp_plugins/dpdk_plugin.so
vpp[5923]: #9 0x00007f51f2aa08fe vlib_call_all_config_functions + 0x88e
vpp[5923]: from /lib/x86_64-linux-gnu/libvlib.so.25.10.0
vpp[5923]: #10 0x00007f51f2aa60f9 vlib_main + 0x529
vpp[5923]: from /lib/x86_64-linux-gnu/libvlib.so.25.10.0
vpp[5923]: #11 0x00007f51f2b164fd vlib_unix_main + 0x81d
vpp[5923]: from /lib/x86_64-linux-gnu/libvlib.so.25.10.0
vpp[5923]: #12 0x00007f51f29645c8 clib_calljmp + 0x18
vpp[5923]: from /lib/x86_64-linux-gnu/libvppinfra.so.25.10.0
Aborted
Why is this message appearing?