On Mar 22, 2024, at 00:53, Samuel Sieb <sam...@sieb.net> wrote:
>> Nothing from the journal tells anything that I understand
>> # journalctl -b -u libvirtd
>> Mar 21 09:31:17 HPZ440.attlocal.net systemd[1]: Starting libvirtd.service -
>> libvirt legacy monolithic daemon...
>> Mar 21 09:31:18 HPZ440.attlocal.net systemd[1]: Started libvirtd.service -
>> libvirt legacy monolithic daemon.
>> Mar 21 09:33:18 HPZ440.attlocal.net systemd[1]: libvirtd.service:
>> Deactivated successfully.
>
> I'm not sure what's going on here. systemd kind of starts it, but then
> apparently either systemd shuts it down or the service decides it has nothing
> to do and quits.
I notice it’s exactly 2 minutes. If you notice the process running, it says it
runs with “--timeout 120”. I wonder if this is the similar to the virtnetworkd
bug we saw last year?
Try disabling the timeout with:
echo LIBVIRTD_ARGS= > /etc/sysconfig/libvirtd && systemctl restart libvirtd
--
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
