Comment # 1 on bug 1177763 from James Fehlig

(In reply to Peter McDonough from comment #0)
> lux-tw:~ # systemctl status libvirtd 
> ��� libvirtd.service - Virtualization daemon
>      Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled;
> vendor preset: disabled)

So far so good, libvirtd is enabled and started after running "Install
hypervisor and tools".

>      Active: inactive (dead) since Thu 2020-10-15 16:55:11 CEST; 4min 7s ago

The service is currently inactive due to the '--timeout 120' option passed to
libvirtd. As seen below, the service started at 16:53:11 and successfully
exited at 16:55:11 (2 minutes later) after no activity.

> TriggeredBy: ��� libvirtd.socket
>              ��� libvirtd-ro.socket

But restarting the service should be triggered by a connection to libvirtd's
unix sockets.

>              ��� libvirtd-admin.socket
>        Docs: man:libvirtd(8)
>              https://libvirt.org
>     Process: 1258 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited,
> status=0/SUCCESS)
>    Main PID: 1258 (code=exited, status=0/SUCCESS)
> 
> Okt 15 16:53:11 lux-tw systemd[1]: Starting Virtualization daemon...
> Okt 15 16:53:11 lux-tw libvirtd[1258]: libvirt version: 6.8.0
> Okt 15 16:53:11 lux-tw libvirtd[1258]: hostname: lux-tw
> Okt 15 16:53:11 lux-tw libvirtd[1258]: Failed to initialize libnetcontrol. 
> Management of interface devices is d>
> Okt 15 16:53:11 lux-tw systemd[1]: Started Virtualization daemon.
> Okt 15 16:55:11 lux-tw systemd[1]: libvirtd.service: Succeeded.

Does libvirt's virsh command line tool work? E.g. 'virsh capabilities' and
'virsh list'?