[Pkg-libvirt-maintainers] Bug#780339: Bug#780339: virt-manager: unable to open new virtual machine dialog
Guido Günther
agx at sigxcpu.org
Thu Mar 12 11:58:25 UTC 2015
severity 780339 normal
thanks
On Thu, Mar 12, 2015 at 11:46:36AM +0100, Arturo Borrero Gonzalez wrote:
> Package: virt-manager
> Version: 1:1.0.1-3
> Severity: important
>
> I open virt-manager and press the 'new virtual machine' button on the top panel.
>
> This is what happens:
>
> $ virt-manager --debug --no-fork
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (cli:187) Launched
> with command line: /usr/share/virt-manager/virt-manager --debug
> --no-fork
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (virt-manager:150)
> virt-manager version: 1.0.1
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (virt-manager:151)
> virtManager import: <module 'virtManager' from
> '/usr/share/virt-manager/virtManager/__init__.pyc'>
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (virt-manager:209)
> GTK version: 3.14.5
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (engine:484)
> libguestfs inspection support: False
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (systray:152)
> Showing systray: False
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (engine:231) About
> to connect to uris ['qemu:///system']
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (manager:216)
> Showing manager
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (engine:385)
> window counter incremented to 1
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (connection:995)
> Scheduling background open thread for qemu:///system
> [jue, 12 mar 2015 11:34:46 virt-manager 2637] DEBUG (connection:1012)
> Background 'open connection' thread is running
> [jue, 12 mar 2015 11:34:49 virt-manager 2637] DEBUG (connection:1063)
> Background open thread complete, scheduling notify
> [jue, 12 mar 2015 11:34:49 virt-manager 2637] DEBUG (connection:1068)
> Notifying open result
> [jue, 12 mar 2015 11:34:49 virt-manager 2637] DEBUG (connection:1074)
> libvirt version=1002009
> [jue, 12 mar 2015 11:34:49 virt-manager 2637] DEBUG (connection:1076)
> daemon version=1002009
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/baseclass.py", line 46, in cb
> return func(*args, **kwargs)
> File "/usr/share/virt-manager/virtManager/connection.py", line 1077,
> in _open_notify
> logging.debug("conn version=%s", self._backend.conn_version())
> File "/usr/share/virt-manager/virtinst/connection.py", line 290, in
> conn_version
> self._conn_version = self._libvirtconn.getVersion()
> File "/usr/lib/python2.7/dist-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
Please show me that libvirt is running nicely already for this
connection. It seems you're lacking a usable hypervisor.
Cheers,
-- Guido
More information about the Pkg-libvirt-maintainers
mailing list