This bug was fixed in the package openvswitch - 2.6.0-0ubuntu2
---
openvswitch (2.6.0-0ubuntu2) yakkety; urgency=medium
* Updates to cover the new way Openvswitch is configurging DPDK (LP: #1625542)
- d/openvswitch-switch.default
- d/openvswitch-switch-dpdk.README.Debian
Fix for openvswitch in the upload queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625542
Title:
--vhost-owner --vhost-perm no more transferred to DPDK EAL commandline
To manage notifications
The changes are purely non-functional.
DPDK was working with the new config as described fine before, to be sure I was
running a few hings over "normal" OVS as built from this just to be sure. This
is the logfile.
** Attachment added: "log running a few tests over openvswitch"
This bug was fixed in the package dpdk - 16.07-0ubuntu5
---
dpdk (16.07-0ubuntu5) yakkety; urgency=medium
[ Christian Ehrhardt ]
* Fix component mismatch by dropping the optional dpdk-pmdinfo tool
(LP: #1630073).
[ Gowrishankar Muthukrishnan ]
* update
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
@jamespage - I think about adding some comment replacing the current DPDK=
config in openvswitch.
So much for the OVS portion of this bug - therefor assigning to myself for now.
** Changed in: openvswitch (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this
Ok, I could adapt the patch in a way to cover server sockets IMHO.
Verification was fine against a ppa at
https://launchpad.net/~paelzer/+archive/ubuntu/dpdk-bug-1625542/+packages.
I'll take a look at preparing an upload if I can complete all other open
tasks tomorrow that would fall into the
If anyone comes by the initial question of this bug.
There is a log entry in "/var/log/openvswitch/ovs-vswitchd.log" that states the
EAL commandline constructed out of the options one configured in the ovsdb.
Example:
"EAL ARGS: ovs-vswitchd -c 0x1 -m 8192 --pci-whitelist :04:00.0
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:
Thanks for the continued test Timo!
Thanks for the patch suggestion and the report that this works in your case
then.
I need to evaluate if the place to call that really changed or if there is more
at stake.
I hope to finalize the setup I need to evaluate that today/tomorrow.
** Changed in:
The attachment "Moves rte_eal_set_socket_permissions() into
vhost_user_create_server()" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated
After a reboot and restart of ovs-vswitchd I have seen these EAL logs
pointing to the problem:
EAL: vhost-user socket cannot set permissions to 0664 (Unknown error -1).
EAL: vhost-user socket unable to set ownership to libvirt-qemu:kvm (Unknown
error -1).
VHOST_CONFIG: vhost-user server: socket
Hi Timo,
it is good that the issue with the unknown parameter are gone now.
The question is now, are these parms:
a) no more passed to OVS, but to DPDK instead (good)
or
b) no more passed to OVS, but neither to DPDK (bad)
If a) is true you should see log entries of these kind each time a DPDK
Hi Christian,
I added the code from fix-vhost-user-socket-permission.patch to my sources
above (running into build issues with 2.6.0~git20160912.dc61b4e-0ubuntu4). This
fixed the unrecognized option '--vhost-owner'.. issue. But the new code is not
used - a new vhu socket is still root:root. I
Hi Timo,
thanks for the feedback.
> Do I still need to apply fix-vhost-user-socket-permission.patch?
Yes, this is to make DPDK EAL having these options.
I'd recommend the packaged versions of dpdk/openvswitch available in Yakkety
as-is - especially once bumped to OVS-2.6-final once released.
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 .
In fact this is the new way
other_config : dpdk-extra: optional string
Specifies additional eal command line arguments for DPDK.
The default is empty. Changing this value requires restarting
the daemon
So it would be something like this before
FYI - I just chimed in on the discussion at https://www.mail-
archive.com/d...@openvswitch.org/msg69706.html
IMHO that would be the cleanest solution, no delta for any package and the same
solution for all distributions.
So anybody getting here with the same issues, please feel free to "vote"
No need to change dpdk identified yet, setting to incomplete for now.
** Changed in: dpdk (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625542
Title:
19 matches
Mail list logo
