For [1], this function had been merged in ocata. The ovs version and qemu version met the requirement if you want to use the vhost_user_client mode. Because this socket will be managed by qemu, it will still exist when the ovs crashes or restart.
Also I think a better approach is to use a separate directory for the vhost_user socket by configure the agent.conf
Please show/verify the configure of vm xml and ovs port.
For [1], this function had been merged in ocata. The ovs version and qemu version met the requirement if you want to use the vhost_user_client mode. Because this socket will be managed by qemu, it will still exist when the ovs crashes or restart.
Also I think a better approach is to use a separate directory for the vhost_user socket by configure the agent.conf
Please show/verify the configure of vm xml and ovs port.
[1] https:/ /bugs.launchpad .net/neutron/ +bug/1604924