Recently, virt-manager is no longer connecting to QEMU, which effectively blocks me from using my VMs.
The problem goes away temporarily after reboot, but returns soon after I leave it for a while after disconnecting.
Relevant logs from journalctl -r:
Jun 16 16:59:21 <my-hostname> virtqemud[14183]: End of file while reading data: Input/output error
Jun 16 16:59:21 <my-hostname> virtqemud[14183]: hostname: <my-hostname>
Jun 16 16:59:21 <my-hostname> virtqemud[14183]: libvirt version: 9.0.0, package: 3.fc38 (Fedora Project, 2023-05-07-17:31:32, )
Jun 16 16:59:14 <my-hostname> audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='>
Jun 16 16:59:14 <my-hostname> systemd[1]: Started virtstoraged.service - Virtualization storage daemon.
Jun 16 16:59:14 <my-hostname> systemd[1]: Starting virtstoraged.service - Virtualization storage daemon...
Jun 16 16:59:14 <my-hostname> kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 16 16:59:14 <my-hostname> kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 16 16:59:14 <my-hostname> kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 16 16:59:13 <my-hostname> systemd[1]: Started virtqemud.service - Virtualization qemu daemon.
Jun 16 16:59:13 <my-hostname> audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='>
Jun 16 16:59:13 <my-hostname> systemd[1]: Starting virtqemud.service - Virtualization qemu daemon...