I had several KVM running on my Leap 15.1 and was working fine.
Today I just updated my machine and restarted afterwards.
virt-manager hanging on connecting and cannot see my VMs.
libvirtdis active and running.
How can I sort this issue?
First step is to collect information about your problem.
- Although you could search your system logs for relevant errors, it might be easier to simply open a console reading your system logs in real time and then invoke. Whatever error is thrown should display immediately You can do this by running the following in a windowed console
journalctl -f
-
Do you have any vms configured to automatically start on boot? Try pinging and connecting to them.
-
Usually carefully watching and understanding what happens when you aren’t able to connect can provide good clues exactly what is running or not. If the virtual network is inaccessible, then you might see a “network not found.” If the connection is actively blocked, then you’ll see a message saying so. If you are able to connect but don’t receive a response, then there is either something blocking on the receiving end or the packet is mis-routed. And so on. To a certain extent, looking for certain responses and understanding what you see might require some experience.
-
Be sure the “Server” serving your VMs is running. You should see your machine’s name or some default name when you open VM Manager, rt-click it to see if it says it’s not running.
As a last resort, if you’re installed on BTRFS you can roll back before your upgrade to see if that works… and then try upgrading again.
TSU
Thank you very much for explanatory advice.
I have stopped/restarted libvirt and network services. restarted machine and it works fine now.
However, still have some issues.
If I runt libvir-manager on terminal :
>sudo virt-manager
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Error starting virt-manager: No graphical display found
and nothing special on
journalctl -f
In the other hand:
>virt-manager
runs virt-manager and I can see all my VMs, However, journalctl -f gives this error
libvirtd[17841]: this function is not supported by the connection driver: virConnectNumOfInterfaces
Anyway, VMs are up and running know.
If I were to hazard a guess,
You probably have services supporting libvirt that already started on boot, so would cause a conflict if you tried to invoke again (The resource is already in use).
My suggestions were meant more to try to understand if something(s) was not starting, and why.
If your virt-manager works when you invoke it, then it sounds like you’ve resolved your problem.
TSU