As replied on the private thread, vpp-echo needs to know about the api prefix you’ve configured (vpp1). Try adding “chroot prefix vpp1” to the list of options.
Regards, Florin > On Jul 1, 2020, at 10:46 AM, sadhanakesa...@gmail.com wrote: > > also i tried to get use-svm-api in existing kernel asa workaround to > establish the tcp ,any fix suggestions? > > -bash-4.2$ sudo > /auto/home.nas04/skesavan/vpp/build-root/install-vpp_debug-native/vpp/bin/vpp_echo > server uri tcp://10.0.0.1/24 use-svm-api > vl_map_shmem:582: region init fail > connect_to_vlib_internal:413: vl_client_api map rv -2 > Timing qconnect:lastbyte > Missing Start Timing Event (qconnect)! > Missing End Timing Event (lastbyte)! > -------- TX -------- > 0 bytes (0 mbytes, 0 gbytes) in 0.000000 seconds > -------- RX -------- > 0 bytes (0 mbytes, 0 gbytes) in 0.000000 seconds > -------------------- > Received close on 0 streams (and 0 Quic conn) > Received reset on 0 streams (and 0 Quic conn) > Sent close on 0 streams (and 0 Quic conn) > Discarded 0 streams (and 0 Quic conn) > -------------------- > Got accept on 0 streams (and 0 Quic conn) > Got connected on 0 streams (and 0 Quic conn) > > Failure Return Status: 42 > ECHO_FAIL_SHMEM_CONNECT (5): shmem connect failed | ECHO_FAIL_CONNECT_TO_VPP > (16): Couldn't connect to vpp | ECHO_FAIL_MISSING_START_EVENT (41): Expected > event qconnect to happen, but it did not! | ECHO_FAIL_MISSING_END_EVENT (42): > Expected event lastbyte to happen, but it did not!-bash-4.2$ sudo > /auto/home.nas04/skesavan/vpp/build-root/install-vpp_debug-native/vpp/bin/vpp_echo > server uri tcp://10.0.0.1/24 use-svm-a > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16860): https://lists.fd.io/g/vpp-dev/message/16860 Mute This Topic: https://lists.fd.io/mt/75236261/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
