FWIW - I tested the “official” 22.02 artifacts using
https://github.com/ayourtch/vpp-relops/tree/master/docker-tests during the
release and it worked the same as the previous releases (I might not be loading
the dpdk plugin during the testing though)
--a
> On 2 Jun 2022, at 14:28, Chinmaya Agg
Hi,
Based on our latest findings for the issue that I was facing regarding dpdk{}
and linux-cp{} sections being present in startup.conf and VPP not coming up, we
found out that if we provide plugin path in the startup.conf, then I don't face
this issue anymore and everything seems to be working
Hi Chinmaya,
Below errors comes when vpp fails to parse startup.conf parameters
like "socket-mem"
, "linux-cp".
seems these options are deprecated in 22.02 version .
vlib_call_all_config_functions: unknown input `dpdk socket-mem 1024 dev
:00:08.0 dev :00:09.0 '
vlib_call_all_config_func
Hi Chinmaya,
1) Check whether the interfaces are bound to dpdk. Grep this on code and
find out the reasin for this. Mostly it will be due to this.
2) Leave a line after socket-mem or comment socket-mem and give only dev
in the next 2 lines and not with space. (just a try)
Regards ,
Akash S R
O
Hi,
As per the suggestions, I modified /etc/vpp/startup.conf file but I am still
facing the same issues. Below is the modified contents of the file:-
dpdk {
socket-mem 1024 dev :00:08.0 dev :00:09.0
}
plugins {
## Adjusting the plugin path depending on where the VPP plugins are
#
Hi,
I have compiled VPP v22.02 on Centos 8.4. I was able to compile it. But when I
installed it and modified /etc/vpp/startup.conf, vpp service is not able to
come up. I added below sections in /etc/vpp/startup.conf:-
dpdk {
socket-mem 1024 dev :00:08.0 dev :00:09.0 dev :00:0a.0 dev
Hoi,
Linux CP's "interface-auto-create" flag is no longer valid. Currently you
can use the following CLI options (see src/plugins/linux-cp/lcp_cli.c):
.short_help = "lcp create | host-if "
.short_help = "lcp lcp-sync [on|enable|off|disable]",
.short_help = "lcp lcp-auto-subint [on|enable|of
