On Tue, 2023-06-20 at 09:16 +0200, Manfred Hollstein wrote:
On Tue, 20 Jun 2023, 08:58:15 +0200, Astris Asperas wrote:
Already Dup-ed to 20230617 here and the problem still persist:
virsh cannot connect to URI:
virsh -c qemu:///system
Until now the temporary solution is the same: restart the LibVirtD
Is the service enabled at all? Also, what does the following command say about libvirtd's status?
$ systemctl status libvirtd.service
This is the status on my system:
○ libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Active: inactive (dead) since Tue 2023-06-20 09:07:51 CEST; 4min 15s ago Duration: 2min 22.414s TriggeredBy: ● libvirtd-ro.socket ● libvirtd-admin.socket ● libvirtd.socket Docs: man:libvirtd(8) https://libvirt.org Process: 8725 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS) Main PID: 8725 (code=exited, status=0/SUCCESS) CPU: 207ms
And I connected successfully using your command at around 09:06:00 CEST
More analysis on virsh log should be needed to clarify the issue.
FWIW, I never saw the issues described in this thread.
HTH, cheers.
l8er manfred
Please check https://bugzilla.suse.com/show_bug.cgi?id=1212195. Regards, Emiliano