Ok It is fixed now. It appears if you enable CONFIG_RTE_LIBRTE_VHOST_USER=y you must have CONFIG_RTE_LIBRTE_VHOST=y as well otherwise it fails at linking stage. Probably is a good idea to add in the documentation. Now I am up and running with traffic.
Thank you Serguei Serguei Bezverkhi, TECHNICAL LEADER.SERVICES Global SP Services [email protected] Phone: +1 416 306 7312 Mobile: +1 514 234 7374 CCIE (R&S,SP,Sec) - #9527 Cisco.com Think before you print. This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Please click here for Company Registration Information. -----Original Message----- From: discuss [mailto:[email protected]] On Behalf Of Serguei Bezverkhi (sbezverk) Sent: Friday, June 19, 2015 3:01 PM To: Justin Pettit Cc: [email protected] Subject: Re: [ovs-discuss] ovs 2.3.2 and dpdk compiling issue You are right, my mistake it was 2.3.90. As per your suggestion I cloned master and tried to compile again, it got much further but still failed with this errors: lib/.libs/libopenvswitch.a(netdev-dpdk.o): In function `netdev_dpdk_vhost_rxq_recv': /root/virtualization/ovs/lib/netdev-dpdk.c:905: undefined reference to `rte_vhost_dequeue_burst' lib/.libs/libopenvswitch.a(netdev-dpdk.o): In function `dpdk_vhost_class_init': /root/virtualization/ovs/lib/netdev-dpdk.c:1738: undefined reference to `rte_vhost_driver_callback_register' lib/.libs/libopenvswitch.a(netdev-dpdk.o): In function `start_vhost_loop': /root/virtualization/ovs/lib/netdev-dpdk.c:1731: undefined reference to `rte_vhost_driver_session_start' lib/.libs/libopenvswitch.a(netdev-dpdk.o): In function `netdev_dpdk_vhost_user_construct': /root/virtualization/ovs/lib/netdev-dpdk.c:640: undefined reference to `rte_vhost_driver_register' lib/.libs/libopenvswitch.a(netdev-dpdk.o): In function `__netdev_dpdk_vhost_send': /root/virtualization/ovs/lib/netdev-dpdk.c:971: undefined reference to `rte_vhost_enqueue_burst' collect2: error: ld returned 1 exit status make[2]: *** [utilities/ovs-testcontroller] Error 1 make[2]: Leaving directory `/root/virtualization/ovs' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/virtualization/ovs' make: *** [all] Error 2 Also According to INSTALL.DPDK this version supports DPDK 2.0. Any suggestions how to fix it? Thank you Serguei Serguei Bezverkhi, TECHNICAL LEADER.SERVICES Global SP Services [email protected] Phone: +1 416 306 7312 Mobile: +1 514 234 7374 CCIE (R&S,SP,Sec) - #9527 Cisco.com Think before you print. This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Please click here for Company Registration Information. -----Original Message----- From: Justin Pettit [mailto:[email protected]] Sent: Friday, June 19, 2015 2:45 PM To: Serguei Bezverkhi (sbezverk) Cc: Daniele Di Proietto; [email protected] Subject: Re: [ovs-discuss] ovs 2.3.2 and dpdk compiling issue > On Jun 19, 2015, at 11:39 AM, Serguei Bezverkhi (sbezverk) > <[email protected]> wrote: > > Hello Daniele, > > Thank you for your reply. What is interesting is that ovs 2.3.1.90 compiled > perfectly fine with dpdk 2.0 so I assumed since 2.3.2 was announced as 2.3.1 > plus bug fixes, it would work fine as well. I assume you mean "2.3.90" (which was master), not "2.3.1.90"; I don't think such a version ever existed. We use ".90" to indicate that the code it contains will be part of the next major release. In this case, 2.3.90 became 2.4.0. If you look at master now, you'll see it's version is 2.4.90, which will become 2.5 or 3.0 depending on what we decide to call it. If you look at branch-2.3, you'll see that it contains the next minor version number 2.3.3, since we don't use the .90 convention for minor releases. > Please let me know how I can clone branch-2.4 and if it still has limitation > of supporting only dpdk 1.6?? I'll leave this one to Daniele. --Justin _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
