On Dec 28, 2024, at 14:00, Robert McBroom via users <users@lists.fedoraproject.org> wrote: > > Have two installations of f41 setup to run virtual machines. On one, all > that is required to get started is to execute "virt-manager" in a terminal > with privilege. On the other, I have to use "systemctl start libvirtd" first > or "virt-manager" doesn't find any of the installed machines. Nothing has > been changed in "/etc/libvirt" configuration files. > > What needs to be set to get the virtual machines to initialize on the second > installation?
If one is upgraded from a prior release that already had libvirtd.service started on boot, it probably still does so you don’t need to start it every boot. In F41 (maybe 40, my memory is foggy with holiday cheer), libvirtd was changed to use socket activation, so it *should* start if the libvirtd.socket is enabled and activated. But I believe there’s service can be started/enabled as well, which is what I do since I have some VMs that start on boot. -- Jonathan Billings -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
