Re: Anyone else seeing libvirtd refusing connections after a day?

[Robert McBroom via users <users@xxxxxxxxxxxxxxxxxxxxxxx>]

Putting

VIRTNETWORKD_ARGS=

in  /etc/sysconfig/virtnetworkd

does nothing. Stopping libvirtd allows virt-manager to connect. Before 
connection

~]# systemctl status libvirtd
● libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; 
preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Tue 2023-06-27 11:05:46 EDT; 23min ago
TriggeredBy: ● libvirtd-ro.socket
             ● libvirtd.socket
             ● libvirtd-admin.socket
       Docs: man:libvirtd(8)
             https://libvirt.org
   Main PID: 2859 (code=exited, status=0/SUCCESS)
      Tasks: 2 (limit: 32768)
     Memory: 29.0M
        CPU: 625ms
     CGroup: /system.slice/libvirtd.service
             ├─2979 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --lea>
             └─2980 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --lea>

Jun 27 11:05:46 HPZ440.attlocal.net systemd[1]: Started libvirtd.service 
- Virtualization dae>
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: started, version 2.89 
cachesize 150
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: compile time options: 
IPv6 GNU-getopt DBus>
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq-dhcp[2979]: DHCP, IP range 
192.168.122.2 -- 192.1>
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq-dhcp[2979]: DHCP, sockets 
bound exclusively to in>
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: reading /etc/resolv.conf
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: using nameserver 
127.0.0.53#53
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: read /etc/hosts - 8 names
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq[2979]: read 
/var/lib/libvirt/dnsmasq/default.addn>
Jun 27 11:05:48 HPZ440.attlocal.net dnsmasq-dhcp[2979]: read 
/var/lib/libvirt/dnsmasq/default>

virt-manager and cockpit cannot connect to the virtual machines

~]# systemctl stop libvirtd
Warning: Stopping libvirtd.service, but it can still be activated by:
  libvirtd-ro.socket
  libvirtd.socket
  libvirtd-admin.socket

Running  virt-manager then connects and works fine.

~]# systemctl status libvirtd
● libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; 
preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Tue 2023-06-27 11:29:52 EDT; 28s ago
TriggeredBy: ● libvirtd-ro.socket
             ● libvirtd.socket
             ● libvirtd-admin.socket
       Docs: man:libvirtd(8)
             https://libvirt.org
   Main PID: 8385 (libvirtd)
      Tasks: 22 (limit: 32768)
     Memory: 62.4M
        CPU: 694ms
     CGroup: /system.slice/libvirtd.service
             ├─2979 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --lea>
             ├─2980 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --lea>
             └─8385 /usr/sbin/libvirtd --timeout 120

Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: internal error: 
Failed to start QEMU bina>
Jun 27 11:29:53 HPZ440.attlocal.net libvirtd[8385]: Failed to probe 
capabilities for /usr/bin>

Binaries that show as failing to start are for minor use processors
_______________________________________________
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