Re: [vpp-dev] Bumping dpdk to 22.11 in vpp 23.02 ?
Add @Xu, Qian Q -Original Message- From: Maciek Konstantynowicz (mkonstan) Sent: Wednesday, January 11, 2023 11:53 PM To: Ji, Kai ; Pei, Yulong ; Xu, Ting ; Liu, Yong ; vpp-dev ; csit-dev Cc: Fan Roy Zhang ; Andrew Yourtchenko (ayourtch) ; Dave Wallace (dwallace) ; Peter Mikus -X (pmikus - PANTHEON TECH SRO at Cisco) Subject: Bumping dpdk to 22.11 in vpp 23.02 ? Hi, On CSIT call just now Kai made us aware of issues with above (cryptodev, sat), as captured in this patch: 37840: dpdk: make impact to VPP for changes in API for DPDK 22.11 | https://gerrit.fd.io/r/c/vpp/+/37840 23.02 RC1 is next week and in CSIT we start testing at RC1 milestone, so it’s very last minute … Also, in the past we got burned by DPDK bump requiring bumping firmware versions on FVL and CVL NICs, which for our performance testbed fleet is a bit of an operation (e.g. on Arm we have to remove the NICs and put them into Xeon machines to do firmware upgrade, unless things improved recently). Asking for views if we could delay dpdk ver bumping to avoid rushing it in, especially that there are open issues? Thoughts? Cheers, -Maciek -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22453): https://lists.fd.io/g/vpp-dev/message/22453 Mute This Topic: https://lists.fd.io/mt/96202380/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] [csit-dev] Bumping dpdk to 22.11 in vpp 23.02 ?
My naive impression looking at the change, seems like it’s still work in progress with several comments open. Especially with the autumn DPDK release IIRC being the “API-breaking” one, looks a bit risky to me… I think haste may get us into places we don’t wanna be in. I would vote to merge this into master post-RC1 milestone, thus giving it more time to soak, and not to put undue strain on anyone. At the same time I would like to (again?) bring up the idea of doing some sort of continuous build/sanity between VPP and DPDK master branches - Fan, I think we discussed this once ? We could then have a change ready “just in time” in the future, potentially ? As I am not well versed with DPDK - does this idea even make sense ? --a > On 11 Jan 2023, at 16:53, Maciek Konstantynowicz (mkonstan) via lists.fd.io > wrote: > > Hi, > > On CSIT call just now Kai made us aware of issues with above (cryptodev, > sat), as captured in this patch: > >37840: dpdk: make impact to VPP for changes in API for DPDK 22.11 | > https://gerrit.fd.io/r/c/vpp/+/37840 > > 23.02 RC1 is next week and in CSIT we start testing at RC1 milestone, so it’s > very last minute … > > Also, in the past we got burned by DPDK bump requiring bumping firmware > versions on FVL and CVL NICs, which for our performance testbed fleet is a > bit of an operation (e.g. on Arm we have to remove the NICs and put them into > Xeon machines to do firmware upgrade, unless things improved recently). > > Asking for views if we could delay dpdk ver bumping to avoid rushing it in, > especially that there are open issues? > > Thoughts? > > Cheers, > -Maciek > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22452): https://lists.fd.io/g/vpp-dev/message/22452 Mute This Topic: https://lists.fd.io/mt/96211041/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] Understanding VRFs and Linux CP
Ahh, ok, I was missing that first step on that post. When issuing the following commands it works as I expected: *vppctl* : ip table add 10 create interface vmxnet3 :0b:00.0 bind set interface ip table vmxnet3-0/b/0/0 10 lcp create vmxnet3-0/b/0/0 host-if ge0 *linux* : sudo ip link add dev vrf-blue type vrf table 10 sudo ip link set dev vrf-blue up sudo ip link set dev ge0 master vrf-blue sudo ip link set dev ge0 up sudo ip addr add 192.168.1.1/24 dev ge0 vpp# show ip fib ipv4-VRF:0, fib_index:0, flow hash:[src dst sport dport proto flowlabel ] epoch:0 flags:none locks:[default-route:1, ] 0.0.0.0/0 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:1 buckets:1 uRPF:0 to:[0:0]] [0] [@0]: dpo-drop ip4 0.0.0.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:2 buckets:1 uRPF:1 to:[0:0]] [0] [@0]: dpo-drop ip4 224.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:4 buckets:1 uRPF:3 to:[0:0]] [0] [@0]: dpo-drop ip4 240.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:3 buckets:1 uRPF:2 to:[0:0]] [0] [@0]: dpo-drop ip4 255.255.255.255/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:5 buckets:1 uRPF:4 to:[0:0]] [0] [@0]: dpo-drop ip4 ipv4-VRF:10, fib_index:1, flow hash:[src dst sport dport proto flowlabel ] epoch:0 flags:none locks:[interface:1, CLI:1, lcp-rt:1, ] 0.0.0.0/0 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:9 buckets:1 uRPF:7 to:[0:0]] [0] [@0]: dpo-drop ip4 0.0.0.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:10 buckets:1 uRPF:8 to:[0:0]] [0] [@0]: dpo-drop ip4 192.168.1.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:20 buckets:1 uRPF:19 to:[0:0]] [0] [@0]: dpo-drop ip4 192.168.1.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:19 buckets:1 uRPF:18 to:[0:0]] [0] [@4]: ipv4-glean: [src:192.168.1.0/24] vmxnet3-0/b/0/0: mtu:9000 next:1 flags:[] 00505694bf900806 192.168.1.1/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:22 buckets:1 uRPF:23 to:[0:0]] [0] [@13]: dpo-receive: 192.168.1.1 on vmxnet3-0/b/0/0 192.168.1.255/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:21 buckets:1 uRPF:21 to:[0:0]] [0] [@0]: dpo-drop ip4 224.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:12 buckets:1 uRPF:10 to:[0:0]] [0] [@0]: dpo-drop ip4 240.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:11 buckets:1 uRPF:9 to:[0:0]] [0] [@0]: dpo-drop ip4 255.255.255.255/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:13 buckets:1 uRPF:22 to:[0:0]] [0] [@13]: dpo-receive: 0.0.0.0 on local0 vpp# Thanks for the help! Cheers, Brian -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22451): https://lists.fd.io/g/vpp-dev/message/22451 Mute This Topic: https://lists.fd.io/mt/96207643/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] Understanding VRFs and Linux CP
Hoi Brian, I think that Linux CP does not consume the netlink message that assigns the interface to a new VRF (table)- doing it the other way around will likely work better. It would be pretty slick if "sudo ip link set dev ge0 master vrf-blue" could pivot the VPP-side interface into the correct table in the dataplane, but that message is not consumed. A previous discussion (and a workaround, which is to put the interface in the table on the VPP side, and then copy that forward into the Linux side as you did above), may work for you. See here: https://lists.fd.io/g/vpp-dev/topic/89678481#20995 If there's a larger interest, I could give it a go, to consume the 'create vrf V' and 'set interface X in vrf V' netlink messages, although this stuff can get tricky :) groet, Pim On Wed, Jan 11, 2023 at 8:48 PM Brian Saunders wrote: > Hello All, > > I've been playing around with VPP and have a question about VRFs created > in linux and how they are supposed to appear within the VPP fib when one > has the Linux CP/NL plugins enabled. I saw the following post here > https://lists.fd.io/g/vpp-dev/topic/89678481#21001 which seemed a little > conflicting on the responses so I just wanted to get a bit of clarification > on the expected behavior. Here are the commands that I'm inputting: > > vppctl commands: > create interface vmxnet3 :0b:00.0 bind > lcp create vmxnet3-0/b/0/0 host-if ge0 > > linux commands: > sudo ip link set ge0 up > sudo ip link add vrf-blue type vrf table 10 > sudo ip link set dev vrf-blue up > sudo ip link set dev ge0 master vrf-blue > sudo ip addr add 192.168.1.1/24 dev ge0 > > From the linux side all is well. When I go into vppctl I see table 10 but > 192.168.1.1/24 is not in table 10. Below if the output from show ip > fib. Is this the expected behavior or should 192.168.1.1/24 be in the > table 10 fib? > > vpp# show ver > vpp v22.10.0-3~gb89dcf824 built by root on ubuntu20 at 2023-01-11T16:05:42 > vpp# show ip fib > ipv4-VRF:0, fib_index:0, flow hash:[src dst sport dport proto flowlabel ] > epoch:0 flags:none locks:[default-route:1, ] > 0.0.0.0/0 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:1 buckets:1 uRPF:0 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 0.0.0.0/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:2 buckets:1 uRPF:1 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 192.168.1.0/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:15 buckets:1 uRPF:14 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 192.168.1.0/24 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:14 buckets:1 uRPF:13 to:[0:0]] > [0] [@4]: ipv4-glean: [src:192.168.1.0/24] vmxnet3-0/b/0/0: mtu:9000 > next:1 flags:[] 00505694bf900806 > 192.168.1.1/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:17 buckets:1 uRPF:18 to:[0:0]] > [0] [@13]: dpo-receive: 192.168.1.1 on vmxnet3-0/b/0/0 > 192.168.1.255/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:16 buckets:1 uRPF:16 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 224.0.0.0/4 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:4 buckets:1 uRPF:3 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 240.0.0.0/4 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:3 buckets:1 uRPF:2 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 255.255.255.255/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:5 buckets:1 uRPF:4 to:[0:0]] > [0] [@0]: dpo-drop ip4 > ipv4-VRF:10, fib_index:1, flow hash:[src dst sport dport proto flowlabel ] > epoch:0 flags:none locks:[lcp-rt:1, ] > 0.0.0.0/0 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:18 buckets:1 uRPF:17 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 0.0.0.0/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:19 buckets:1 uRPF:19 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 224.0.0.0/4 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:21 buckets:1 uRPF:21 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 240.0.0.0/4 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:20 buckets:1 uRPF:20 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 255.255.255.255/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:22 buckets:1 uRPF:23 to:[0:0]] > [0] [@13]: dpo-receive: 0.0.0.0 on local0 > vpp# > > Thanks, > > Brian > > > > -- Pim van Pelt PBVP1-RIPE - http://www.ipng.nl/ -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22450): https://lists.fd.io/g/vpp-dev/message/22450 Mute This Topic: https://lists.fd.io/mt/96207643/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Understanding VRFs and Linux CP
Hello All, I've been playing around with VPP and have a question about VRFs created in linux and how they are supposed to appear within the VPP fib when one has the Linux CP/NL plugins enabled. I saw the following post here https://lists.fd.io/g/vpp-dev/topic/89678481#21001 which seemed a little conflicting on the responses so I just wanted to get a bit of clarification on the expected behavior. Here are the commands that I'm inputting: vppctl commands: create interface vmxnet3 :0b:00.0 bind lcp create vmxnet3-0/b/0/0 host-if ge0 linux commands: sudo ip link set ge0 up sudo ip link add vrf-blue type vrf table 10 sudo ip link set dev vrf-blue up sudo ip link set dev ge0 master vrf-blue sudo ip addr add 192.168.1.1/24 dev ge0 >From the linux side all is well. When I go into vppctl I see table 10 but 192.168.1.1/24 is not in table 10. Below if the output from show ip fib. Is this the expected behavior or should 192.168.1.1/24 be in the table 10 fib? vpp# show ver vpp v22.10.0-3~gb89dcf824 built by root on ubuntu20 at 2023-01-11T16:05:42 vpp# show ip fib ipv4-VRF:0, fib_index:0, flow hash:[src dst sport dport proto flowlabel ] epoch:0 flags:none locks:[default-route:1, ] 0.0.0.0/0 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:1 buckets:1 uRPF:0 to:[0:0]] [0] [@0]: dpo-drop ip4 0.0.0.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:2 buckets:1 uRPF:1 to:[0:0]] [0] [@0]: dpo-drop ip4 192.168.1.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:15 buckets:1 uRPF:14 to:[0:0]] [0] [@0]: dpo-drop ip4 192.168.1.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:14 buckets:1 uRPF:13 to:[0:0]] [0] [@4]: ipv4-glean: [src:192.168.1.0/24] vmxnet3-0/b/0/0: mtu:9000 next:1 flags:[] 00505694bf900806 192.168.1.1/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:17 buckets:1 uRPF:18 to:[0:0]] [0] [@13]: dpo-receive: 192.168.1.1 on vmxnet3-0/b/0/0 192.168.1.255/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:16 buckets:1 uRPF:16 to:[0:0]] [0] [@0]: dpo-drop ip4 224.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:4 buckets:1 uRPF:3 to:[0:0]] [0] [@0]: dpo-drop ip4 240.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:3 buckets:1 uRPF:2 to:[0:0]] [0] [@0]: dpo-drop ip4 255.255.255.255/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:5 buckets:1 uRPF:4 to:[0:0]] [0] [@0]: dpo-drop ip4 ipv4-VRF:10, fib_index:1, flow hash:[src dst sport dport proto flowlabel ] epoch:0 flags:none locks:[lcp-rt:1, ] 0.0.0.0/0 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:18 buckets:1 uRPF:17 to:[0:0]] [0] [@0]: dpo-drop ip4 0.0.0.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:19 buckets:1 uRPF:19 to:[0:0]] [0] [@0]: dpo-drop ip4 224.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:21 buckets:1 uRPF:21 to:[0:0]] [0] [@0]: dpo-drop ip4 240.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:20 buckets:1 uRPF:20 to:[0:0]] [0] [@0]: dpo-drop ip4 255.255.255.255/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:22 buckets:1 uRPF:23 to:[0:0]] [0] [@13]: dpo-receive: 0.0.0.0 on local0 vpp# Thanks, Brian -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22449): https://lists.fd.io/g/vpp-dev/message/22449 Mute This Topic: https://lists.fd.io/mt/96207643/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Bumping dpdk to 22.11 in vpp 23.02 ?
Hi, On CSIT call just now Kai made us aware of issues with above (cryptodev, sat), as captured in this patch: 37840: dpdk: make impact to VPP for changes in API for DPDK 22.11 | https://gerrit.fd.io/r/c/vpp/+/37840 23.02 RC1 is next week and in CSIT we start testing at RC1 milestone, so it’s very last minute … Also, in the past we got burned by DPDK bump requiring bumping firmware versions on FVL and CVL NICs, which for our performance testbed fleet is a bit of an operation (e.g. on Arm we have to remove the NICs and put them into Xeon machines to do firmware upgrade, unless things improved recently). Asking for views if we could delay dpdk ver bumping to avoid rushing it in, especially that there are open issues? Thoughts? Cheers, -Maciek -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22448): https://lists.fd.io/g/vpp-dev/message/22448 Mute This Topic: https://lists.fd.io/mt/96202380/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] Error message on starting vpp
Merged :)
Thanks,
-daw-
On 1/11/23 9:31 AM, Ahmed Abdelsalam (ahabdels) via lists.fd.io wrote:
I just discussed this with Nathan. Should be merged soon. Cheers!
*From: *Pim van Pelt
*Date: *Wednesday, 11 January 2023 at 13:37
*To: *vpp-dev@lists.fd.io
*Cc: *jul...@klaiber.me , Pablo Camarillo
(pcamaril) , Ahmed Abdelsalam (ahabdels)
*Subject: *Re: [vpp-dev] Error message on starting vpp
Hoi,
Nathan's fix is still pending and starting VPP at HEAD still emits the
warning:
pim@hippo:~/src/vpp$ make run
WARNING: STARTUP_CONF not defined or file doesn't exist.
Running with minimal startup config: unix { interactive
cli-listen /run/vpp/cli.sock gid 1000 } dpdk { no-pci } \n
vnet_feature_arc_init:272: feature node 'ip6-lookup' not found (before
'pt', arc 'ip6-output')
I see the other fixes from this thread were merged (thanks!) but what
about the OP? Would be prudent to address before Jan 18th :)
groet,
Pim
On Mon, Dec 19, 2022 at 9:49 AM Nathan Skrzypczak
wrote:
Hi Xiaodong,
It seems like a '.runs_after' was introduced on a node that does
not belong to the arc in question. [0] should solve this.
(CCingJulian as he is the author of the original patch & sr plugin
maintainers)
Cheers
-Nathan
[0] https://gerrit.fd.io/r/c/vpp/+/37837
Le sam. 3 déc. 2022 à 19:29, Xiaodong Xu a
écrit :
Hi VPP experts,
I got the following error message when starting vpp recently:
0: vnet_feature_arc_init:272: feature node 'ip6-lookup' not
found (before 'pt', arc 'ip6-output')
I'm using master branch from VPP git repo. By checking the
source code, it seems it might have something to do with the
comment
https://github.com/FDio/vpp/commit/b79d09bbfa93f0f752f7249ad27a08eae0863a6b
and
https://github.com/FDio/vpp/commit/39d6deca5f71ee4fe772c10d76ed5b65d1ebec44
So I remove the two commits from my local repo and the issue
is gone.
The message seems to be harmless, but if anyone who is
familiar with the commits can take a look, I'd appreciate it.
Regards,
Xiaodong
--
Pim van Pelt
PBVP1-RIPE - http://www.ipng.nl/
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22447): https://lists.fd.io/g/vpp-dev/message/22447
Mute This Topic: https://lists.fd.io/mt/95432703/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] Error message on starting vpp
I just discussed this with Nathan. Should be merged soon. Cheers!
From: Pim van Pelt
Date: Wednesday, 11 January 2023 at 13:37
To: vpp-dev@lists.fd.io
Cc: jul...@klaiber.me , Pablo Camarillo (pcamaril)
, Ahmed Abdelsalam (ahabdels)
Subject: Re: [vpp-dev] Error message on starting vpp
Hoi,
Nathan's fix is still pending and starting VPP at HEAD still emits the warning:
pim@hippo:~/src/vpp$ make run
WARNING: STARTUP_CONF not defined or file doesn't exist.
Running with minimal startup config: unix { interactive cli-listen
/run/vpp/cli.sock gid 1000 } dpdk { no-pci } \n
vnet_feature_arc_init:272: feature node 'ip6-lookup' not found (before 'pt',
arc 'ip6-output')
I see the other fixes from this thread were merged (thanks!) but what about the
OP? Would be prudent to address before Jan 18th :)
groet,
Pim
On Mon, Dec 19, 2022 at 9:49 AM Nathan Skrzypczak
mailto:nathan.skrzypc...@gmail.com>> wrote:
Hi Xiaodong,
It seems like a '.runs_after' was introduced on a node that does not belong to
the arc in question. [0] should solve this.
(CCingJulian as he is the author of the original patch & sr plugin maintainers)
Cheers
-Nathan
[0] https://gerrit.fd.io/r/c/vpp/+/37837
Le sam. 3 déc. 2022 à 19:29, Xiaodong Xu
mailto:stid.s...@gmail.com>> a écrit :
Hi VPP experts,
I got the following error message when starting vpp recently:
0: vnet_feature_arc_init:272: feature node 'ip6-lookup' not found (before 'pt',
arc 'ip6-output')
I'm using master branch from VPP git repo. By checking the source code, it
seems it might have something to do with the comment
https://github.com/FDio/vpp/commit/b79d09bbfa93f0f752f7249ad27a08eae0863a6b and
https://github.com/FDio/vpp/commit/39d6deca5f71ee4fe772c10d76ed5b65d1ebec44
So I remove the two commits from my local repo and the issue is gone.
The message seems to be harmless, but if anyone who is familiar with the
commits can take a look, I'd appreciate it.
Regards,
Xiaodong
--
Pim van Pelt mailto:p...@ipng.nl>>
PBVP1-RIPE - http://www.ipng.nl/
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22446): https://lists.fd.io/g/vpp-dev/message/22446
Mute This Topic: https://lists.fd.io/mt/95432703/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] Error message on starting vpp
Hoi,
Nathan's fix is still pending and starting VPP at HEAD still emits the
warning:
pim@hippo:~/src/vpp$ make run
WARNING: STARTUP_CONF not defined or file doesn't exist.
Running with minimal startup config: unix { interactive
cli-listen /run/vpp/cli.sock gid 1000 } dpdk { no-pci } \n
vnet_feature_arc_init:272: feature node 'ip6-lookup' not found (before
'pt', arc 'ip6-output')
I see the other fixes from this thread were merged (thanks!) but what about
the OP? Would be prudent to address before Jan 18th :)
groet,
Pim
On Mon, Dec 19, 2022 at 9:49 AM Nathan Skrzypczak <
nathan.skrzypc...@gmail.com> wrote:
> Hi Xiaodong,
>
> It seems like a '.runs_after' was introduced on a node that does not
> belong to the arc in question. [0] should solve this.
> (CCingJulian as he is the author of the original patch & sr plugin
> maintainers)
>
> Cheers
> -Nathan
>
> [0] https://gerrit.fd.io/r/c/vpp/+/37837
>
> Le sam. 3 déc. 2022 à 19:29, Xiaodong Xu a écrit :
>
>> Hi VPP experts,
>>
>> I got the following error message when starting vpp recently:
>>
>> 0: vnet_feature_arc_init:272: feature node 'ip6-lookup' not found (before
>> 'pt', arc 'ip6-output')
>>
>> I'm using master branch from VPP git repo. By checking the source code,
>> it seems it might have something to do with the comment
>> https://github.com/FDio/vpp/commit/b79d09bbfa93f0f752f7249ad27a08eae0863a6b
>> and
>> https://github.com/FDio/vpp/commit/39d6deca5f71ee4fe772c10d76ed5b65d1ebec44
>>
>> So I remove the two commits from my local repo and the issue is gone.
>>
>> The message seems to be harmless, but if anyone who is familiar with the
>> commits can take a look, I'd appreciate it.
>>
>> Regards,
>> Xiaodong
>>
>>
>>
>>
>
>
>
--
Pim van Pelt
PBVP1-RIPE - http://www.ipng.nl/
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22445): https://lists.fd.io/g/vpp-dev/message/22445
Mute This Topic: https://lists.fd.io/mt/95432703/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] One week before 23.02 RC1 milestone
Hi all, Just a kind reminder that as per the release schedule [0], next Wednesday 18 January 2023 at noon UTC I will pull the stable/2302 branch. After that, only fixed and pre-agreed low risk commits will be accepted on that branch in preparation for the release. [0] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_23.02 --a /* your friendly 23.02 release manager */ -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22444): https://lists.fd.io/g/vpp-dev/message/22444 Mute This Topic: https://lists.fd.io/mt/96197939/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] linux-cp endianness issue
Hoi folks, I noticed that linux-cp plugin is not quite right with endianness: Example code: lcp_add = vpp.api.lcp_itf_pair_add_del_v2(is_add=True, sw_if_index=17, host_if_type=VppEnum.vl_api_lcp_itf_host_type_t.LCP_API_ITF_HOST_TAP, host_if_name="loop0", netns="dataplane") print(lcp_add) lcp_ret = vpp.api.lcp_itf_pair_get() print(lcp_ret) Before (note an incorrect host_sw_if_index in the return, is *301989888, *expected *18*): VPP version is 23.02-rc0~212-gf06a518f8 lcp_itf_pair_add_del_v2_reply(_0=103, context=2, retval=0, *host_sw_if_index=301989888*) (lcp_itf_pair_get_reply(_0=105, context=3, retval=0, cursor=4294967295), [lcp_itf_pair_details(_0=106, context=3, phy_sw_if_index=17, *host_sw_if_index=18*, vif_index=594, host_if_name='loop0', host_if_type=, netns='dataplane')]) After: VPP version is 23.02-rc0~212-gf06a518f8 lcp_itf_pair_add_del_v2_reply(_0=103, context=2, retval=0, *host_sw_if_index=18*) (lcp_itf_pair_get_reply(_0=105, context=3, retval=0, cursor=4294967295), [lcp_itf_pair_details(_0=106, context=3, phy_sw_if_index=17, host_sw_if_index=18, vif_index=595, host_if_name='loop0', host_if_type=, netns='dataplane')]) See https://gerrit.fd.io/r/c/vpp/+/37894 -- Pim van Pelt PBVP1-RIPE - http://www.ipng.nl/ -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22443): https://lists.fd.io/g/vpp-dev/message/22443 Mute This Topic: https://lists.fd.io/mt/96197927/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
