Thank you Christian for one of best explanation I have seen! IT WAS MY TYPO not bug, and I got everything work. This problem was so strange that I made second clean install system. It worked.
I MADE TYPO to /etc/network/interfaces conf file, bridge definition: ... auto kvmbr0 iface kvmbr0 inet static bridge ports none #must be "bridge_ports none", with _ (underscore) not space ... No errors in syslog and dmesg, just ... no bridge. - How "/var/run/libvirt/virtquemud-sock" (with additional "u") catches up I don't understand, "grep -rnw '/etc/' -e 'virtqemud-sock'" shows nothing, also /var, /root, /usr and other searchable folders under /. So this spelling may be binary, somewhere in code. Now commented out entire bridge definition in /etc/network/interfaces , so no bridge: virt-install [virtual machine definition] shows again "/var/run/libvirt/virtquemud-sock", yes with additional "u". but virsh handles missing bridge very well: virsh start win2016 #virtual is defined previously error: Failed to start domain win2016 error: Cannot get interface MTU on 'kvmbr0': No such device Seems like that wrong spelling "virtquemud-sock" and the whole misleading errormessage comes from virt-install or it's dependencies. Probably "no bridge" error-handling goes unhandled and wild. Sorry for false bugalarm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925228 Title: libvirtd failed to connect to socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1925228/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
