![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1215984
https://bugzilla.suse.com/show_bug.cgi?id=1215984#c15
--- Comment #15 from James Fehlig
I don't know about modular vs monolithic daemons.
Yeah, and you really shouldn't have to. Unfortunately for Leap, the systemd presets do not include libvirtd. It is included in the SLE15 SP5 presets, and the TW presets contain all the required modular daemons. With the correct presets, the daemon(s) are started when the packages are installed.
Like how is anybody ever supposed to get this running?
As Charles mentioned, you can install with roles, patterns, or the yast module. If those don't suite your needs, you can install a functional libvirt+kvm stack with zypper install libvirt-daemon-qemu libvirt-client On SLE15 SP5 or TW, that should get you a working setup with necessary daemons enabled and started. 'virsh list --all; virsh net-list --all; virsh pool-list --all' should all work without further configuration. I tried installing those packages on a fresh Leap 15.5 install, and the virsh commands worked fine after I enabled/started libvirtd (systemctl enable libvirtd.service; systemctl start libvirtd.service). I then installed virt-manager, started it as a normal user, and it connected to the system daemon just fine after providing root passwd. BTW, I'm using packages from the standard 15.5 update repos, nothing from the Virtualization project. -- You are receiving this mail because: You are on the CC list for the bug.