Hi Ivan, thanks for the report and your help to make Ubuntu better. I must admit I haven't seen this in all the time that 20.04 is out already.
I was checking logs of default installs of various Ubuntu versions but that problem doesn't seem to happen by default. > To me, more enduser than Ubuntu specialist, seems like "virtquemud-sock" has > excess "u" after > "q", must be "virtqemud-sock". Indeed - if you look at the source you'll find plenty of "virtqemud" but no "virtquemud". TBH the /var/run/libvirt/virtqemud-sock (even if not mistyped) would be part of the so called "split daemon" approach which Ubuntu didn't switch to yet (not even in 21.04). I haven't found a mention of the right (nor the wrong) name in virt- manager (which is the code base of virt-install) either. Due to monolithic and split daemon being allowed in parallel what happens is probing for split and then fallback to the monolithic daemon then. That I can see in my logs as well: Apr 15 11:11:00 Keschdeichel libvirtd[160109]: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory But that isn't a real problem - it is probing one and then using the present, working former approach. Also the above (my example) only happened with a virsh that was part of a git-build and therefore was looking for split daemons - nothing that really is in the archive of Ubuntu 20.04. My guess atm is that somewhere on your system must be a custom config or a custom build of some of the tools here that refers to "virtquemud-sock". Does $ grep -Hrn quemud /etc/ show anything on your affected system? Thanks for providing steps to reproduce, I was trying your steps and also again simplifying them: Note (FYI): step 4 and 5 of your steps are not needed as that is default after install of libvirt-daemon-system package. $ apt install libvirt-daemon-system $ virt-install --name u --ram 1024 --disk path=/var/lib/libvirt/images/ubuntu1804.qcow2,size=8 --vcpus 1 --os-type linux --os-variant generic --graphics none --location 'http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/' The above installs and does not trigger the error you described. Since I knew that I had it in my logs from when I was experimenting with other builds I was looking back at the tweaks I've done and one was debug-logs. So I set /etc/libvirt/libvirtd.conf to log_level = 2 log_outputs="2:syslog:libvirtd" But even with that I can't trigger the issue as reported. So let me try to summarize: 1. split daemons is a config option in recent libvirt >5.7, but not used in Ubuntu builds 2. the missed socket of /var/run/libvirt/virtqemud-sock would be part of the split daemon virtqemud.service which we don't ship 3. the typo to "/var/run/libvirt/virtquemud-sock" would be in config files for virtqemud.service which we don't ship I recommend checking your local system for: - custom config that might have triggered this - custom builds that expect or set up split daemons Extra Question: I know that some behaviro of libvirt and virsh and such tools do depend on environment variables, do you get the same issue when you do not log in as root but as normal user (use virt-install with sudo then) ? ** Changed in: libvirt (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/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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
