Solution: when virt-manager doesn't start (fresh installed tumbleweed)

English Virtualization
1

Problem

(Fresh installed tumbleweed)

After following

  • YaST
  • Virtualization
  • Install Hypervisor and Tools
  • KVM server & or KVM tools

the app ‘Virtual Machine Manager’ crashes itself without any message.

In terminal, $ virt-manager shows error:

> virt-manager
Traceback (most recent call last):
  File "/usr/bin/virt-manager", line 6, in <module>
    from virtManager import virtmanager
  File "/usr/share/virt-manager/virtManager/virtmanager.py", line 19, in <module>
    from virtinst import BuildConfig
  File "/usr/share/virt-manager/virtinst/__init__.py", line 9, in <module>
    gi.require_version('Libosinfo', '1.0')
    ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.13/site-packages/gi/__init__.py", line 129, in require_version
    raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Libosinfo not available

Solution

sudo zypper in libosinfo-devel

you may also need

  • sudo systemctl start libvirtd
  • or sudo systemctl enable libvirtd --now

I spent hours to solve this :face_holding_back_tears:

2

You only need typelib-1_0-Libosinfo-1_0 which is pulled in as dependency by libosinfo-devel.

3

Thank you for fixing my mistake!

Actually I’m doing snapshot backup because I got another similar errors and installed many random packages.

I will update original post after organising stuff.

4

And you really need to open bug report for virt-manager so the correct dependency is added to the package. https://bugzilla.opensuse.org/, same user/password as here.

5

Right. This is the bug we call about. I forgot that.

I wrote bug report:
https://bugzilla.opensuse.org/show_bug.cgi?id=1241119