Hello,
I am testing DHCP client feature from VPP stack (v22.02) onto our system.
My setup is: I run k8s cluster on x86 system in which I have a pod which uses
VPP stack and it accesses physical NIC interface using DPDK and SR-IOV. There
are two physical interfaces which we use in VPP, one of
Hello community,
I need your help regarding statistic data extraction in vpp.
Any suggestion or reference would be helpful.
Thanks,
Dibas
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22649): https://lists.fd.io/g/vpp-dev/message/22649
Mute
Hello,
I followed the guide here
https://fdio-vpp.readthedocs.io/en/latest/usecases/vhost/vhost.html and get
into an issue as the VM running over libvirt (6.0.0) is not receiving the
traffic from the bare metal machine.
I'm using Ubuntu 20.04.3 LTS and I run VPP version:
vpp# show ver
vpp
Do you see a response to the DHCP Discover packets?
What does the vpp packet tracer show?
Thanks... Dave
> On Mar 2, 2023, at 7:03 AM, Thakur, Anagha wrote:
>
>
>
> Hello,
>
> I am testing DHCP client feature from VPP stack (v22.02) onto our system.
>
> My setup is: I run k8s cluster
Hoi,
Can you be more specific on 'statistic data extraction' What numbers/data
are you looking for?
Take a look at the 'stats segment' which you might address read-only using
/run/vpp/stats.sock or mount as a FUSE filesystem with
https://s3-docs.fd.io/vpp/22.06/developer/extras/vpp_stats_fs.html
Hi Benjamin,
Can you please take a look at
https://www.redhat.com/en/blog/hands-vhost-user-warm-welcome-dpdk and
especially the part for 'numa' configuration for the KVM guest?
Xiaodong
On Thu, Mar 2, 2023 at 9:24 AM Benjamin Vandendriessche
wrote:
>
> Hello,
>
> I followed the guide here
>
I do see DHCP Offer in the packet tracer from the Server which I have set up on
the other side.
But VPP does not send any DHCP Request out, instead I always see that VPP
continuously keeps sending DHCP Discovery.
I have attached tx and rx pcap trace in my prevous email.
Best Regards,
Anagha
It is likely that you are missing memAccess=’shared’
https://fdio-vpp.readthedocs.io/en/latest/usecases/vhost/xmlexample.html#:~:text=%3Ccell%20id%3D%270%27%20cpus%3D%270%27%20memory%3D%27262144%27%20unit%3D%27KiB%27%20memAccess%3D%27shared%27/%3E
From: on behalf of Benjamin Vandendriessche
The dhcp client has a number of “show error” counters. Do you see any of the error counters increasing? The packet trace I’d like to see would be from “trace add 1000” … “show trace max 1000” or similar. The pcap trace implies that the dhcp offer packets are dropped, but we need to work out why…
There is something in the DHCP OFFER the client does not like and moves back to
new DHCP session. Or the DHCP OFFER never made it to the client.
Hemant
From: vpp-dev@lists.fd.io On Behalf Of Thakur, Anagha
Sent: Thursday, March 02, 2023 4:02 PM
To: vpp-dev@lists.fd.io
Subject: Re:
Hi
when I use vpp-2110, vlib_worker_thread_node_refork vm->node_main.node_by_name
is pointer to main thread,but when main thread node_by_name hash_vec resize and
resize buffer not continuation cause worker thread vm->node_main.node_by_name
is wild pointer，so I want modified
Thank you both, that fixed my issue.
Note that when using the config from
https://fdio-vpp.readthedocs.io/en/latest/usecases/vhost/xmlexample.html#:~:text=%3Ccell%20id%3D%270%27%20cpus%3D%270%27%20memory%3D%27262144%27%20unit%3D%27KiB%27%20memAccess%3D%27shared%27/%3E
it
results in a kernel panic
Hi Sudhir,
Is your issue resolved?
Actually we are facing same issue on vpp.2106.
In our case "api-rx-ring" is not getting called.
in our usecase workers are calling some functions in main-thread context
leading to RPC message and memory is allocated from api section.
This leads to Api-segment
Hi Chetan,
In our case we are observing this issue occasionally exact steps to
recreate the issue are not known.
I made changes to our process node as suggested by dave and with these
changes trying to recreate the issue.
Soon I will update my results and findings in this mail thread.
Thanks
14 matches
Mail list logo
