Am 21.03.2024 um 21:51 schrieb Samuel Sieb samuel@sieb.net:
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@lists.fedoraproject.org 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.
As you noticed:
systemctl status libvirtd ● libvirtd.service - libvirt legacy monolithic daemon
^^^^^^^^^^^^^^^^^
Fedora uses the current modularized version
See: - https://fedoraproject.org/wiki/Changes/LibvirtModularDaemons - https://libvirt.org/daemons.html#switching-to-modular-daemons
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy@fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast