KVM Problem mit Virtuel Maschine Manager

[letzter3]

Hallo zusammen.
Ein OMV als KVM-Host.
Auf einem Mageia Linux soll der VMM laufen.

Code: Alles auswählen

[letzter@wuerfel ~]$ virt-manager --debug                          
[So, 02 Apr 2017 17:01:02 virt-manager 404] DEBUG (cli:187) Launched with command line: /usr/share/virt-manager/virt-manager --debug
[So, 02 Apr 2017 17:01:02 virt-manager 404] DEBUG (virt-manager:148) virt-manager version: 1.1.0
[So, 02 Apr 2017 17:01:02 virt-manager 404] DEBUG (virt-manager:149) virtManager import: <module 'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'>
[So, 02 Apr 2017 17:01:02 virt-manager 404] DEBUG (virt-manager:207) GTK version: 3.14.8
[So, 02 Apr 2017 17:01:02 virt-manager 404] DEBUG (engine:455) libguestfs inspection support: False
[So, 02 Apr 2017 17:01:02 virt-manager 404] DEBUG (systray:150) Showing systray: False
[So, 02 Apr 2017 17:01:02 virt-manager 404] DEBUG (engine:229) About to connect to uris ['qemu+ssh://root@192.168.0.12/system']
[So, 02 Apr 2017 17:01:02 virt-manager 404] DEBUG (manager:208) Showing manager
[So, 02 Apr 2017 17:01:02 virt-manager 404] DEBUG (engine:356) window counter incremented to 1
[So, 02 Apr 2017 17:01:06 virt-manager 404] DEBUG (connection:946) Scheduling background open thread for qemu+ssh://root@192.168.0.12/system
[So, 02 Apr 2017 17:01:06 virt-manager 404] DEBUG (connection:960) Background 'open connection' thread is running
root@192.168.0.12's password: 
[So, 02 Apr 2017 17:01:18 virt-manager 404] DEBUG (connection:1011) Background open thread complete, scheduling notify
[So, 02 Apr 2017 17:01:18 virt-manager 404] DEBUG (connection:1016) Notifying open result
[So, 02 Apr 2017 17:01:18 virt-manager 404] DEBUG (connection:1022) libvirt version=1002009
[So, 02 Apr 2017 17:01:18 virt-manager 404] DEBUG (connection:1024) daemon version=9012
[So, 02 Apr 2017 17:01:18 virt-manager 404] DEBUG (connection:882) conn.close() uri=qemu+ssh://root@192.168.0.12/system
[So, 02 Apr 2017 17:01:18 virt-manager 404] DEBUG (engine:572) ['ssh', 'root']
[So, 02 Apr 2017 17:01:18 virt-manager 404] DEBUG (error:80) error dialog message:
summary=Mit libvirt konnte nicht verbunden werden.

internal error Cannot find suitable emulator for x86_64

Stellen Sie sicher, dass der «libvirtd»-Daemon
auf dem entfernten Host läuft.
details=Mit libvirt konnte nicht verbunden werden.

internal error Cannot find suitable emulator for x86_64

Stellen Sie sicher, dass der «libvirtd»-Daemon
auf dem entfernten Host läuft.

Libvirt URI is: qemu+ssh://root@192.168.0.12/system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1025, in _open_notify
    logging.debug("conn version=%s", self._backend.conn_version())
  File "/usr/share/virt-manager/virtinst/connection.py", line 294, in conn_version
    self._conn_version = self._libvirtconn.getVersion()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3697, in getVersion
    if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self)
libvirtError: internal error Cannot find suitable emulator for x86_64
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
^C[So, 02 Apr 2017 17:03:32 virt-manager 404] DEBUG (cli:182) Uncaught exception:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/baseclass.py", line 163, in cb
    def cb():
KeyboardInterrupt

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/baseclass.py", line 163, in cb
    def cb():
KeyboardInterrupt
[So, 02 Apr 2017 17:03:40 virt-manager 404] DEBUG (manager:219) Closing manager
[So, 02 Apr 2017 17:03:40 virt-manager 404] DEBUG (engine:360) window counter decremented to 0
/usr/share/virt-manager/virtManager/baseclass.py:108: Warning: Source ID 7 was not found when attempting to remove it
  GLib.source_remove(handle)
/usr/share/virt-manager/virtManager/engine.py:381: Warning: Source ID 7 was not found when attempting to remove it
  GLib.source_remove(self.timer)
[So, 02 Apr 2017 17:03:40 virt-manager 404] DEBUG (engine:442) Exiting app normally.

libvirt läuft und mittels Konsole kann ich auch auf den Host zugreifen.

Code: Alles auswählen

[letzter@wuerfel ~]$ virsh --connect qemu+ssh://root@192.168.0.12/system
root@192.168.0.12's password: 
Willkommen bei virsh, dem interaktiven Virtualisierungsterminal.

Tippen Sie:  'help' für eine Hilfe zu den Befehlen
       'quit' zum Beenden

virsh # 

Meine Suche hat keine Lösung gebracht
Wie bekomme ich den VMM zum laufen?

[letzter3]

Mittlerweile crosspost https://forums.mageia.org/de/viewtopic.php?f=8&t=3050, da es anscheinend am Clientrechner liegt.