Libvirtd Fails to Launch First Time

[Ken Swenson]

Hello,

I'm having a quite odd issue with libvirtd. I have it set to start on
boot via systemd service, however it seems to fail and the service
'succeeds' and does not continue running the daemon. There is nothing in
the journal logs however the libvirtd debug logs seem to show

    2020-08-08 13:55:26.362+0000: 1386: debug : virCommandRunAsync:2619
    : About to run ip link set lo netns -1
    2020-08-08 13:55:26.362+0000: 1386: debug : virFileClose:134 :
    Closed fd 26
    2020-08-08 13:55:26.362+0000: 1386: debug : virFileClose:134 :
    Closed fd 28
    2020-08-08 13:55:26.362+0000: 1386: debug : virFileClose:134 :
    Closed fd 30
    2020-08-08 13:55:26.362+0000: 1386: debug : virCommandRunAsync:2621
    : Command result 0, with PID 1610
    2020-08-08 13:55:26.390+0000: 1386: debug : virCommandRun:2461 :
    Result fatal signal 2, stdout: '' stderr: 'RTNETLINK answers: No
    such process

I am not sure if this is relevant to the problem or not as I do not see
anything else in the logs that indicates an issue during the launch
process, other than many file descriptors closing but I assume that is
normal. If I then start libvirtd a second time after it has been
launched once it runs fine. I don't believe it is a race condition on
boot as if I disable the auto start and manually start it it will still
fail in the same way the first time.

If anyone has any ideas on what I may be able to check to fix this I
would really appreciate it. It has been bugging me for some time now.

Thank you,

Ken

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20200808/a8f09a60/attachment.htm>