Comment 4 for bug 1625542

See my results below.
When restarting ovs-vswitchd it complains: unrecognized option '--vhost-owner'

I use ovs master (2.6.90) and dpdk 16.07. Do I still need to apply fix-vhost-user-socket-permission.patch?

Result:
---------
ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-extra="--vhost-owner libvirt-qemu:kvm --vhost-perm 0664"

root@compute29:/var/run/openvswitch# ovs-vsctl get Open_vSwitch . other_config
{dpdk-extra="--vhost-owner libvirt-qemu:kvm --vhost-perm 0664", dpdk-init="true", dpdk-lcore-mask="0x300", dpdk-socket-mem="4096,4096"}

root@compute29:/var/run/openvswitch# export DB_SOCK=/var/run/openvswitch/db.sock
root@compute29:/var/run/openvswitch# ovs-vswitchd unix:$DB_SOCK -vconsole:emer -vsyslog:err -vfile:info --mlockall --no-chdir \
> --log-file=/var/log/openvswitch/ovs-vswitchd.log \
> --pidfile=/var/run/openvswitch/ovs-vswitchd.pid \
> --detach \
> --monitor
ovs-vswitchd: unrecognized option '--vhost-owner'
EAL: Detected 32 lcore(s)
ovs-vswitchd: unrecognized option '--vhost-owner'

Versions:
----------
root@compute29:/usr/src/ovs# ovs-vsctl --version
ovs-vsctl (Open vSwitch) 2.6.90
DB Schema 7.14.0

dpdk 16.07
(from: http://dpdk.org/browse/dpdk/snapshot/dpdk-16.07.zip)