[Bug 1625542] Re: --vhost-owner --vhost-perm no more transferred to DPDK EAL commandline

[ChristianEhrhardt]

FYI - I got to pass all other bits of my DPDK tests and got to the point where this is recreated.
I collected a few other minor bugs along the way that need fixes (which is what made it taking a while), but now I'm able to take a deeper look at your patch.

horsea ovs-vswitchd[31620]: EAL: vhost-user socket cannot set permissions to 0666 (Unknown error -1).
horsea ovs-vswitchd[31620]: EAL: vhost-user socket unable to set ownership to libvirt-qemu:kvm (Unknown error -1).

-- 
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