Spot on! The script qemu-ifup was indeed the cause of the problem. It's a dummy script that only does "exit 0" and it was apparently needed in the past with old versions of libvirt. I see examples on the net where it is used to configure interfaces with shell commands. I don't need it. I see that everything works fine without the <script path="/opt/oa/etc/qemu-ifup"/> line, for vhostuser and ethernet interfaces. Are there any side effects or can I safely remove that line? Thanks again! Riccardo On 22 February 2018 at 20:55, Laine Stump <laine@redhat.com> wrote:
[...]
<interface type="vhostuser"> <script path="/opt/oa/etc/qemu-ifup"/>
^^^^^^^^^^^^^^^^ Why do you have this line?
Spo> $ virsh create vm.xml
error: Failed to create domain from vm.xml error: unsupported configuration: scripts are not supported on interfaces of type vhostuser
This error message tells you exactly what is wrong. The <script> element is only supported for interfaces of type='ethernet' - these are interfaces for which a tap device is created, but it's not connected to anything; the purpose of the script is to connect the tap to device to [something user-defined]. Other types of interface (e.g. vhost-user) should have enough intelligence built into the code to perform all necessary setup.
Do you actually have something in this qemu-ifup file?
The logs from libvirtd.log say: 2018-02-22 09:18:24.982+0000: 2033: warning : qemuProcessStartWarnShmem:4539 : Detected vhost-user interface without any shared memory, the interface might not be operational 2018-02-22 09:18:24.982+0000: 2033: error : qemuBuildHostNetStr:3894 : unsupported configuration: scripts are not supported on interfaces of type vhostuser
The logs from qemu simply say: 2018-02-22 09:26:15.857+0000: shutting down, reason=failed
And finally, ovs-vswitchd.log: 2018-02-22T09:18:24.715Z|00328|dpdk|INFO|VHOST_CONFIG: vhost-user client: socket created, fd: 51 2018-02-22T09:18:24.716Z|00329|netdev_dpdk|INFO|vHost User device '0.vm' created in 'client' mode, using client socket '/opt/oa/vhost/0.vm.sock' 2018-02-22T09:18:24.718Z|00330|dpdk|WARN|VHOST_CONFIG: failed to connect to /opt/oa/vhost/0.vm.sock: No such file or directory 2018-02-22T09:18:24.718Z|00331|dpdk|INFO|VHOST_CONFIG: /opt/oa/vhost/0.vm.sock: reconnecting... 2018-02-22T09:18:24.718Z|00332|bridge|INFO|bridge switch1: added interface 0.vm on port 5
Am I missing something on the openvswitch or on the libvirt side?
It looks like openvswitch can't find /opt/oa/vhost/0.vm.sock, but isn't either openvswitch or libvirt in charge of creating it? Then, I'm not too sure about the error messages in libvirtd.log...
My software versions are: libvirt 3.10.0, qemu 2.10.2, openvswitch 2.8.1 and DPDK 17.11.
Thanks a lot!
Riccardo
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users