https://bugzilla.suse.com/show_bug.cgi?id=1213743 https://bugzilla.suse.com/show_bug.cgi?id=1213743#c2 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #2 from James Fehlig <jfehlig@suse.com> --- Agree it's a duplicate, but might not be visible to the reporter since it's a SLE bug. From comment 10 of that bug: --- Support for modular daemons can be thought of in two phases. The first phase is making clients aware of modular daemons. They should be able to work equally well with monolithic libvirtd or modular daemons. This phase is what I aim to fix here by building the library with support for modular daemons. The second phase is switching new deployments from the monolithic libvirtd to modular daemons. This phase has been done in Factory/Tumbleweed and is under consideration for SLE15 SP6 via jira PED-4804. --- Some workarounds until the fix reaches Leap 15.5: 1. Specify the connection URI directly, e.g. 'virsh -c qemu:///system list'. Optionally add the URI to 'uri_default' in /etc/libvirt/libvirt.conf or in LIBVIRT_DEFAULT_URI env variable to avoid specifying it each time you use virsh or other libvirt client. 2. Enable and start virtproxyd.service. It proxies client connections on the old monolithic socket (/var/run/libvirt/libvirt-sock) to the appropriate modular daemon socket. *** This bug has been marked as a duplicate of bug 1213352 *** -- You are receiving this mail because: You are on the CC list for the bug.