[Bug 1625542] Re: --vhost-owner --vhost-perm no more transferred to DPDK EAL commandline
ChristianEhrhardt
1625542 at bugs.launchpad.net
Tue Oct 4 10:23:26 UTC 2016
For OVS the change to the config is ready for review.
On update a user of the former DPDK_OPTS will get the common:
Configuration file '/etc/default/openvswitch-switch'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
And when looking at it is is obvious what was going on for the user:
--- /etc/default/openvswitch-switch 2016-10-04 10:06:19.043458386 +0000
+++ /etc/default/openvswitch-switch.dpkg-new 2016-10-04 09:07:08.000000000 +0000
@@ -7,5 +7,13 @@
# a suitable place to specify --ovs-vswitchd-wrapper=valgrind.
# OVS_CTL_OPTS=
-# DPDK options - see /usr/share/doc/openvswitch-common/INSTALL.DPDK.md.gz
-DPDK_OPTS='--dpdk -c 0x1 -n 4'
+# DPDK options are now configured via ovs-vsctl/ovsdb, see:
+# - /usr/share/doc/openvswitch-common/INSTALL.DPDK.md.gz
+# - /usr/share/doc/openvswitch-common/INSTALL.DPDK-ADVANCED.md.gz
+# dpdk-extra is the fallback for users who formerly set e.g.
+# '--vhost-owner libvirt-qemu:kvm --vhost-perm 0664'
+# here or any other DPDK EAL arguments via DPDK_OPTS which are not covered by
+# the default switches provided by ovs-vsctl.
+# This is an arbitrary string that will get appended to the EAL commandline.
+# For more on the new ovsdb based configuration of DPDK features, see:
+# `man ovs-vswitchd.conf.db`
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1625542
Title:
--vhost-owner --vhost-perm no more transferred to DPDK EAL commandline
Status in dpdk package in Ubuntu:
Triaged
Status in openvswitch package in Ubuntu:
Triaged
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=/var/log/openvswitch/ovs-vswitchd.log \
--pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor
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://help.ubuntu.com/16.04/serverguide/DPDK.html#dpdk-openvswitch
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://openvswitch.org/support/dist-docs/INSTALL.DPDK-
ADVANCED.md.html for most of the new other_config values.
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://openvswitch.org/support/dist-docs/ovs-
vswitchd.conf.db.5.html.
But since neither DPDK nor OVS took the ownership control patches
(https://www.mail-archive.com/dev@openvswitch.org/msg69706.html) it
has to be a delta that we add once we have final OVS 2.6.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1625542/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list