On Sat, 28 Dec 2024 at 19: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?
>
You probably just need to enable the libvirtd service on-boot for the
second machine. Compare the following on each system:
$ sudo systemctl status libvirtd
For reference this is my current system:
[wmcdonald@fedora ~ ]$ sudo systemctl status libvirtd.service
○ libvirtd.service - libvirt legacy monolithic daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled;
preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf, 50-keep-warm.conf
Active: inactive (dead)
TriggeredBy: ○ libvirtd-ro.socket
○ libvirtd.socket
○ libvirtd-admin.socket
Docs: man:libvirtd(8)
https://libvirt.org/
If it's not in 'enabled' state on the second system, then the service won't
be starting on boot which explains the difference in behaviour. And Francis
has already supplied:
$ sudo systemctl enable libvirtd.service #(starts for all future boots)
$ sudo systemctl start libvirtd.service #(starts in the current boot)
More reading at:
https://docs.fedoraproject.org/en-US/quick-docs/systemd-understanding-and-administering/
--
_______________________________________________
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
