--vhost-owner --vhost-perm no more transferred to DPDK EAL commandline
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpdk (Ubuntu) |
Fix Released
|
High
|
Christian Ehrhardt | ||
openvswitch (Ubuntu) |
Fix Released
|
Medium
|
Christian Ehrhardt |
Bug Description
Hi,
this was reported by an early tester of OVS 2.6 / DPDK 16.07 packages in yakkety.
TL;DR
- the old --vhost-owner --vhost-perm seem no more to be passed to the DPDK commandline
- OVS complains about ovs-vswitchd: unrecognized option '--vhost-owner'
Example:
ovs-vswitchd \
--vhost-owner libvirt-qemu:kvm \
--vhost-perm 0664 \
-- unix:$DB_SOCK -vconsole:emer -vsyslog:err -vfile:info \
--mlockall --no-chdir \
--log-file=
--pidfile=
ovs-vswitchd: unrecognized option '--vhost-owner'
I expect this to be either of these two:
- actually those should be after a --dpdk switch to get to the DPDK EAL commandline. Just how we describe it at https:/
OR
- An upstream change on OVS 2.6 now interferes and breaks the passing of these options. A lot was changed to push DPDK config to the ovsdb so this can be possible.
See http://
I expect to be the second more than the first case due to DPDK configuration being completely changed into an ovsdb based operation. Search for dpdk here http://
But since neither DPDK nor OVS took the ownership control patches (https://<email address hidden>
No need to change dpdk identified yet, setting to incomplete for now.