Bug 1500161 - With vhostuser_mode set to 'client', qemu is not able to connect to the vhostuser socket.
Summary: With vhostuser_mode set to 'client', qemu is not able to connect to the vhost...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-neutron
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ga
: 12.0 (Pike)
Assignee: Tim Rozet
QA Contact: Itzik Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2017-10-10 05:56 UTC by yogananth subramanian
Modified: 2018-10-18 07:22 UTC (History)
8 users (show)

Fixed In Version: puppet-neutron-11.3.0-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 22:13:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1722917 0 None None None 2017-10-11 21:08:54 UTC
OpenStack gerrit 511337 0 None None None 2017-10-11 21:09:34 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description yogananth subramanian 2017-10-10 05:56:42 UTC
Description of problem:
With vhostuser_mode set to 'client', qemu is not able to connect to the vhostuser socket.

There is path mismatch between the vhostuser socket path created by qemu and openvswitch.
/var/run/openvswitch/vhu_6c1313cf-1: Failed to connect socket: No such file or directory
netdev_dpdk|INFO|Socket /var/run/openvswitch/vhu6c1313cf-18 created for vhost-user port vhu6c1313cf-18

From the above output it can be noticed that, the qemu expects prefix "vhu_" while openvswitch just "vhu" and the last character ('8') in the openvswitch vhostuser socket name is missing from qemu,i.e., "vhu_6c1313cf-1" instead of "vhu_6c1313cf-18"

Version-Release number of selected component (if applicable):
Puddle used 2017-09-27.3

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Tim Rozet 2017-10-11 13:23:14 UTC
Can you please provide the output of 'ovs-vsctl list open_vswitch' on your ovs dpdk compute node?

Comment 2 yogananth subramanian 2017-10-11 15:40:24 UTC
[root@overcloud-computeovsdpdk-0 heat-admin]# ovs-vsctl list open_vswitch
_uuid               : 88465d32-ff7a-4d03-b20d-958e45f06779
bridges             : [6df07e87-ec38-4ec9-b91d-cbf6fd09a451, 8ca492cc-c239-4793-8b28-9f9910decf7a]
cur_cfg             : 21
datapath_types      : [netdev, system]
db_version          : "7.15.0"
external_ids        : {hostname="overcloud-computeovsdpdk-0", "odl_os_hostconfig_config_odl_l2"="{  \"supported_vnic_types\": [{    \"vnic_type\": \"normal\",    \"vif_type\": \"vhostuser\",    \"vif_details\": {      \"uuid\": \"88465d32-ff7a-4d03-b20d-958e45f06779\",      \"has_datapath_type_netdev\": true,      \"port_prefix\": \"vhu_\",      \"vhostuser_socket_dir\": \"/var/lib/vhost_sockets\",      \"vhostuser_ovs_plug\": true,      \"vhostuser_mode\": \"client\",      \"vhostuser_socket\": \"/var/lib/vhost_sockets/vhu_$PORT_ID\"    }  }],  \"allowed_network_types\": [\"local\",\"vlan\",\"vxlan\",\"gre\"],  \"bridge_mappings\": {\"dpdknet\":\"br-link\"}}", odl_os_hostconfig_hostid="overcloud-computeovsdpdk-0.localdomain", system-id="e03f63f3-b7e7-409c-b645-a180b03fe6f5"}
iface_types         : [dpdk, dpdkr, dpdkvhostuser, dpdkvhostuserclient, geneve, gre, internal, lisp, patch, stt, system, tap, vxlan]
manager_options     : [340a8ef1-5313-4168-9694-fb08d809fa43, 3c976efb-0126-4899-b3e0-8cf8a7225dfc]
next_cfg            : 21
other_config        : {dpdk-extra="-n 4", dpdk-init="true", dpdk-lcore-mask="3ff", dpdk-socket-mem="4096,4096", local_ip="", pmd-cpu-mask="c00c00", provider_mappings="dpdknet:br-link"}
ovs_version         : "2.7.2"
ssl                 : []
statistics          : {}
system_type         : rhel
system_version      : "7.4"

Comment 3 Nir Yechiel 2017-10-17 10:21:20 UTC
Merged and cherry picked to stable/pike

Comment 9 errata-xmlrpc 2017-12-13 22:13:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.