Do you see DPDK library in the path mentioned
path-to-dpdk/x86_64-ivshmem-linuxapp-gcc/lib/libdpdk.a?
From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of Vivek Gupta
Sent: Tuesday, March 29, 2016 7:40 AM
To: gowrishankar
Cc: discuss@openvswitch.org
Subject: Re: [ovs-discuss] Cann
Set my path-to-dpdk to homedirectory/dpdk2.2/ x86_64-ivshmem-linuxapp-gcc and
this should resolve your issue.
Regards,
Bhanu Prakash.
From: Vivek Gupta [mailto:vive...@hcl.com]
Sent: Tuesday, March 29, 2016 10:15 AM
To: Bodireddy, Bhanuprakash ; gowrishankar
Cc: discuss@openvswitch.org
Subject
Hello Vivek,
I quickly verified the issue you reported and could reproduce it. When one use
install target 'x86_64-ivshmem-linuxapp-gcc' the directory layout is slightly
different.
make install T= x86_64-ivshmem-linuxapp-gcc DESTDIR=install creates
'/dpdk2.2/install/share/dpdk/ x86_64-native-
thanks for your prompt reply but changing the path-to-dpdk does not bring any breakthrough.
I am able to run helloworld example ,provided in DPDK thus I don't see any issue with DPDK installation.
I was analying the config.log file and found that undefined reference to libpcap.so and libpthre
Initially I had tried with
with-dpdk= homedirectory/dpdk2.2/install/share/dpdk/x86_64-native-linuxapp-gcc but nothing happened. then switched to
with-dpdk=homedirectory/dpdk2.2/ x86_64-ivshmem-linuxapp-gcc but problem is as it is.
Did I commited any wrong step in DPDK installations? My steps a
I don't see an issue with the steps you mentioned here. Can you try using a
static library instead of shared library.
Replace CONFIG_RTE_BUILD_SHARED_LIB=n and reinstall the DPDK library(you should
see libdpdk.a) and see if this makes a difference?
Regards,
Bhanu Prakash.
From: Vivek Gupta
Hi
Thanks for suggestion.
Reinstalling the DPDK with
"CONFIG_RTE_BUILD_SHARED_LIB=n" worked.
I am very much curious to know any future impact of setting "CONFIG_RTE_BUILD_SHARED_LIB=n" and why it didn't worked for
CONFIG_RTE_BUILD_SHARED_LIB=Y?
Thanks & Regards
Vivek
From: Bodireddy, Bha
On Mon, Mar 28, 2016 at 6:56 PM, John McDowall <
jmcdow...@paloaltonetworks.com> wrote:
> Russell,
>
> Thanks of taking the time to provide a detailed response. Let me try and
> answer your questions, and ask a few on my own.
>
>1. Yes, I want to continue working through this as we see it real
On 28 March 2016 at 18:42, Richa wrote:
> Hi Guru,
>
> Thanks for quick reply. Yes, you guessed it right - I do have ovs2.4.0 and
> 2.5.0.
>
> I expected new version to take over, as I followed the "upgrading" steps
> described here -
>
> https://github.com/openvswitch/ovs/blob/master/INSTALL.md
Hi Guru,
Thanks for quick reply. Yes, you guessed it right - I do have ovs2.4.0 and
2.5.0.
I expected new version to take over, as I followed the "upgrading" steps
described here -
https://github.com/openvswitch/ovs/blob/master/INSTALL.md
I guess I must have missed something in those steps
Dear all,
I cross-compile OVS to ARM target board, and copied ovs-vswitchd to target
board.
Then
./ovs-vswitched
It indicated:
./ovs-vswitchd: error while loading shared libraries: librt.so.1 : cannot open
shared object file: No such file or directory
I copied librt.so.1 and ln -s to librt-2.
Dear all,
When type in
./ovs-vswitchd.
The target ARM box shows:
Ovs-vswitchd: /dev/urandom: read error (No such file or directory)
Seems urandom cannot be download from internet.
So, what can I do ?
Thanks
Kai
___
discuss mailing list
discuss@openvs
12 matches
Mail list logo
