On 3/21/24 12:20, Robert McBroom via users wrote:
On 3/20/24 10:32 AM, Jerry James wrote:
On Wed, Mar 20, 2024 at 7:49 AM Robert McBroom via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Recently libvirtd.service is not starting on boot. I have to manually
start it with systemctl start libvirtd.
Do I need to put that command in a startup script?
libvirtd.service is socket activated, so it should run automatically
when needed. Does something not work if you don't start it manually?
virt- manager starts but says it cannot connect to anything. I have six
virtual machines I use for various purposes.
systemctl status libvirtd
shows disabled and dead. After starting it manually all machines are
present.
Status then shows
systemctl status libvirtd
●libvirtd.service - libvirt legacy monolithic daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled;
preset: disabled)
Thought
systemctl enable libvirtd
would change the preset notation but it didn't
It doesn't. That's the system preset. "enable" only changes the first
enabled/disable option, but that overrides the preset, so it should be
starting at boot if you've rebooted since changing that setting.
You can use "journalctl -b -u libvirtd" to find out what has happened.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
