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

[Robert McBroom]

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

Anyone else seeing libvirtd refusing connections after a day?

[Barry]

>  On 27 Jun 2023, at 17:51, Robert McBroom via users
> <users(a)lists.fedoraproject.org&gt; wrote:
>  
>  Putting
>  
>  VIRTNETWORKD_ARGS=
>  
>  in  /etc/sysconfig/virtnetworkd
>  
>  does nothing. Stopping libvirtd allows virt-manager to connect. Before connection 
Does the info here help?
https://discussion.fedoraproject.org/t/libvirtd-stop-responding-after-som...

Barry

Anyone else seeing libvirtd refusing connections after a day?

[Robert McBroom]

On 6/27/23 14:02, Barry wrote:
> > On 27 Jun 2023, at 17:51, Robert McBroom via users 
> > <users(a)lists.fedoraproject.org&gt; wrote:
> >
> > Putting
> >
> > VIRTNETWORKD_ARGS=
> >
> > in  /etc/sysconfig/virtnetworkd
> >
> > does nothing. Stopping libvirtd allows virt-manager to connect. 
> > Before connection
>
>  Does the info here help? 
>  https://discussion.fedoraproject.org/t/libvirtd-stop-responding-after-som...
Seems like a red herring

systemctl stop libvirtd

works a lot simpler and keeps working even with

~]# systemctl status virtnetworkd
○ virtnetworkd.service - Virtualization network daemon
      Loaded: loaded (/usr/lib/systemd/system/virtnetworkd.service; 
disabled; preset: disabled)
     Drop-In: /usr/lib/systemd/system/service.d
              └─10-timeout-abort.conf
      Active: inactive (dead)
TriggeredBy: ○ virtnetworkd-ro.socket
              ○ virtnetworkd-admin.socket
              ○ virtnetworkd.socket
        Docs: man:virtnetworkd(8)
              https://libvirt.org

Additional VMs start without problems. so what is the function of 
virtnetworkd?

Anyone else seeing libvirtd refusing connections after a day?

[Barry]

>  On 28 Jun 2023, at 00:15, Robert McBroom via users
> <users(a)lists.fedoraproject.org&gt; wrote:
>  
>  Seems like a red herring 
I know there are systemd changes that are supposed to fix this in testing.
I thought that was referred to in the discuss thread.

Barry

Anyone else seeing libvirtd refusing connections after a day?

[Robert McBroom]

On 6/28/23 03:21, Barry wrote:
> > On 28 Jun 2023, at 00:15, Robert McBroom via
> users<users(a)lists.fedoraproject.org>  wrote:
> >
> > Seems like a red herring
>  I know there are systemd changes that are supposed to fix this in testing.
>  I thought that was referred to in the discuss thread.
>  
 From man virtnetworkd

        It is one of a collection of modular daemons that replace 
functionality  previously
        provided by the monolithic libvirtd daemon.

Looks like pieces haven't made it through the update process. with 
libvirtd still providing all the services.