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
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
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 '
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
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
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
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
Hi Vijay,
Ok, too bad...
Could you also share the output of `show log` ?
Cheers
-Nathan
Le lun. 22 mars 2021 à 19:20, Vijay Kumar a écrit :
> Hi Nathan,
>
> Even with the rebuild based on the steps you provided, the result is same.
>
>
>
> Regards.
>
>
> On Mon, 22 Mar 2021, 19:01 Nathan
Hi Nathan,
Even with the rebuild based on the steps you provided, the result is same.
Regards.
On Mon, 22 Mar 2021, 19:01 Nathan Skrzypczak,
wrote:
> Hi Vijay,
>
> Usually the `unknown input dpdk` comes from the dpdk plugin not being
> loaded at startup. So either there is a
> `plugins {
Hi Vijay,
Usually the `unknown input dpdk` comes from the dpdk plugin not being
loaded at startup. So either there is a
`plugins { plugin dpdk_plugin.so { disable } }` stanza that was added to
you config file - but VM restart wouldn't explain this.
Or vpp-ext-deps / e-build containing dpdk got
Hi Chetan,
I added the PCI address into the whitelist configuration of the startup.conf
Yes I did load both kernel modules: uio and pci_generic
Pls find the output that you asked for.
root@ubuntu-10-37-3-75:~/VPP-NEW/vpp/build-root/install-vpp_debug-native/vpp/bin#
lsmod | grep uio
igb_uio
Hi Vijay,
Have you modprobe uio and uio_pci_generic ?
kindly confirm the pci address of your nic again using ethtool -i
Please share what else is coming on the console.
Thanks,
Chetan
On Mon, Mar 22, 2021 at 1:58 PM Vijay Kumar wrote:
> Hi,
>
> I was running VPP on my VM without any issues.
Hi,
I was running VPP on my VM without any issues. But recently due to a lab
maintenance, the VM was powered off. But now I am not able to bring it up.
Getting the error "unknown input dpdk dev :0b:00.0"
-- I have ensured the ethernet interface is set to DOWN so that VPP takes
control of
13 matches
Mail list logo
