On 11/23/18 12:02 PM, Ramzah Rehman wrote: [...] > #validating > > ovs-vsctl get Open_vSwitch . dpdk_initialized > # got message "ovs-vsctl: Open_vSwitch does not contain a column whose > name matches "dpdk_initialized"" > ovs-vswitchd --version > # got message "ovs-vswitchd (Open vSwitch) 2.9.4 DPDK 17.11.4" > ovs-vsctl get Open_vSwitch . dpdk_version > # got message "ovs-vsctl: Open_vSwitch does not contain a column whose > name matches "dpdk_version"" > > Even though I followed all steps, ovs-vsctl get Open_vSwitch . > dpdk_initialized gives ovs-vsctl: Open_vSwitch does not contain a > column whose name matches "dpdk_initialized" error. Please help.
I believe the docs are not up to date. I was struggling with this too so I would like to suggest you to: - turn the DEBUG on for dpdk related parts of OvS: ovs-appctl vlog/list <- to get the names of modules ovs-appctl vlog/set ...:dbg <- to set debug (e.g. dpdk:file:dbg and netdef_dpdk:file:dbg) I usually turn on file:dbg on all dpdk related modules (that you get from the list) and 'tail -f' ovs-vswitchd.log to see what is going on. You should see something like: 2018-11-23T11:18:02.186Z|00019|dpdk|INFO|DPDK Enabled - initialized when DPDK gets initialized (this is INFO level so you don't have to switch to debug - but I suggest it anyway when you are starting with DPDK). Regards Andrzej _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
