Tumbleweed snapshot 20230616 broke kvm
Hello, has anyone also experienced issues with kvm after updating from snapshot 20230614 to 20230616? I was able to start virt-manager this morning but it could not connect to the VMs. 20230616 installed libvirt-* 9.4.0-3.1. After going back to 20230614 (libvirt-* 9.4.0-2.2), I saw my VMs again and was able to start them again. virt-manager.log shows no error messages. I could not analyze the problem further yet, because I need KVM for my home office work and I had to get back to work. -- PGP Public Key available at https://pgp.mit.edu/ Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507
Same problem here: Windows Guest on KMV Host and Virt Manager can't connect to qemu:///system Rapid workaround, to get back to work: restar the LibVirt Daemon: sudo systemctl restart libvirtd Hope this works, as in my case.
Am 19.06.23 um 12:21 schrieb Astris Asperas:
Same problem here: Windows Guest on KMV Host and Virt Manager can't connect to qemu:///system
Rapid workaround, to get back to work:
restar the LibVirt Daemon:
sudo systemctl restart libvirtd
Hope this works, as in my case.
I installed 20230616 yesterday, system was shut down over night and started this morning for work. But thanks for your answer, will do some tests after work. -- PGP Public Key available at https://pgp.mit.edu/ Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507
Qemu + KVM here has began failing to start due to internal error some snapshot before then 16 June: sudo journalctl -u libvirtd.service | grep 'internal error: Cannot' giu 14 08:19:21 AsusN752Host libvirtd[7440]: internal error: Cannot find start time for pid 4704 giu 14 08:19:21 AsusN752Host libvirtd[7440]: internal error: Cannot find start time for pid 4837 giu 15 09:00:12 AsusN752Host libvirtd[32607]: internal error: Cannot find start time for pid 32207 giu 15 22:50:10 AsusN752Host libvirtd[29695]: internal error: Cannot find start time for pid 29616 giu 16 08:33:32 AsusN752Host libvirtd[8810]: internal error: Cannot find start time for pid 5842 giu 16 08:33:32 AsusN752Host libvirtd[8810]: internal error: Cannot find start time for pid 8740 giu 16 22:27:09 AsusN752Host libvirtd[10612]: internal error: Cannot find start time for pid 10430 giu 19 08:25:22 AsusN752Host libvirtd[8045]: internal error: Cannot find start time for pid 7775 Since then, the solution has been to restart the LibVirtD after the KDE Desktop has finished to load. The VirtManager can then connect to qemu://System again. Hope this help.
Am 19.06.23 um 16:28 schrieb Astris Asperas:
Qemu + KVM here has began failing to start due to internal error some snapshot before then 16 June:
sudo journalctl -u libvirtd.service | grep 'internal error: Cannot'
giu 14 08:19:21 AsusN752Host libvirtd[7440]: internal error: Cannot find start time for pid 4704 giu 14 08:19:21 AsusN752Host libvirtd[7440]: internal error: Cannot find start time for pid 4837 giu 15 09:00:12 AsusN752Host libvirtd[32607]: internal error: Cannot find start time for pid 32207 giu 15 22:50:10 AsusN752Host libvirtd[29695]: internal error: Cannot find start time for pid 29616 giu 16 08:33:32 AsusN752Host libvirtd[8810]: internal error: Cannot find start time for pid 5842 giu 16 08:33:32 AsusN752Host libvirtd[8810]: internal error: Cannot find start time for pid 8740 giu 16 22:27:09 AsusN752Host libvirtd[10612]: internal error: Cannot find start time for pid 10430 giu 19 08:25:22 AsusN752Host libvirtd[8045]: internal error: Cannot find start time for pid 7775
Since then, the solution has been to restart the LibVirtD after the KDE Desktop has finished to load.
The VirtManager can then connect to qemu://System again.
Hope this help.
Snapshot 20230617 contains a fix for virt-manager: ==== virt-manager ==== Subpackages: virt-install virt-manager-common - bsc#1212195 - libvirtd crashes when virt-manager connects virt-manager qemu:///system on a fresh installation tumbleweed virtman-check-for-libvirt-modular-daemons.patch - Changes to osinfo-db cause some virt-manager tests to fail. virtman-fix-osinfo-tests.patch So I will try to install 20230616 + 20230617 tomorrow and check if the problems are fixed with these updates. Thanks for your help! -- PGP Public Key available at https://pgp.mit.edu/ Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507
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 More analysis on virsh log should be needed to clarify the issue.
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
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
participants (4)
-
Astris Asperas -
Emiliano Langella -
Manfred Hollstein -
Oliver Schwabedissen