Virt-manager will exit with error 'internal error Cannot find suitable emulator for x86_64'

Bug #920853 reported by Vladimir Skubriev
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Virt-manager will exit with error 'internal error Cannot find suitable emulator for x86_64'

In the latest updates for ubuntu 12.04.

There is a bug in upstream of virt-manager.

See Redhat bug tracker.

https://bugzilla.redhat.com/show_bug.cgi?id=726167

Redhat is fixed all today.

What about ubuntu 12.04 ?

Revision history for this message
Vladimir Skubriev (v-skubriev) wrote :

Error polling connection 'qemu:///system': internal error Cannot find suitable emulator for x86_64

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 440, in _tick
    conn.tick()
  File "/usr/share/virt-manager/virtManager/connection.py", line 1414, in tick
    newNets, self.nets) = self._update_nets()
  File "/usr/share/virt-manager/virtManager/connection.py", line 1277, in _update_nets
    lookup_func, build_class)
  File "/usr/share/virt-manager/virtManager/connection.py", line 1209, in _poll_helper
    if not check_support():
  File "/usr/share/virt-manager/virtManager/connection.py", line 501, in is_network_capable
    virtinst.support.SUPPORT_CONN_NETWORK)
  File "/usr/lib/python2.7/dist-packages/virtinst/support.py", line 574, in check_conn_support
    return _check_support(conn, feature, conn)
  File "/usr/lib/python2.7/dist-packages/virtinst/support.py", line 443, in _check_support
    actual_drv_ver = _hv_ver(conn, uri)
  File "/usr/lib/python2.7/dist-packages/virtinst/support.py", line 376, in _hv_ver
    ret = cmd(*args)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2884, in getVersion
    if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self)
libvirtError: internal error Cannot find suitable emulator for x86_64

Revision history for this message
Vladimir Skubriev (v-skubriev) wrote :

0.8.6-1ubuntu8 repeat last bug, see next:

Exception in thread Tick thread:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 505, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/share/virt-manager/virtManager/engine.py", line 428, in _tick
    conn.tick()
  File "/usr/share/virt-manager/virtManager/connection.py", line 1462, in tick
    oldNets, self.nets) = self._update_nets()
  File "/usr/share/virt-manager/virtManager/connection.py", line 1107, in _update_nets
    virtinst.support.SUPPORT_CONN_NETWORK)
  File "/usr/lib/python2.7/dist-packages/virtinst/support.py", line 574, in check_conn_support
    return _check_support(conn, feature, conn)
  File "/usr/lib/python2.7/dist-packages/virtinst/support.py", line 443, in _check_support
    actual_drv_ver = _hv_ver(conn, uri)
  File "/usr/lib/python2.7/dist-packages/virtinst/support.py", line 376, in _hv_ver
    ret = cmd(*args)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2884, in getVersion
    if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self)
libvirtError: internal error Cannot find suitable emulator for x86_64

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virt-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for reporting this issue. Are you able to reproduce it with virtinst 0.600.1 that is now in Precise?

Changed in virt-manager (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Vladimir Skubriev (v-skubriev) wrote : Re: [Bug 920853] Re: Virt-manager will exit with error 'internal error Cannot find suitable emulator for x86_64'

25.02.2012 1:02, Marc Deslauriers пишет:
> Thanks for reporting this issue. Are you able to reproduce it with
> virtinst 0.600.1 that is now in Precise?
>
> ** Changed in: virt-manager (Ubuntu)
> Status: Confirmed => Incomplete
>
Excusme! I fifnished my experiments. And now not have a time for this work.

This is a true/real problem.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for virt-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in virt-manager (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Evren Yurtesen (eyurtese-g) wrote :

I am having the same problem and virtualization is enabled in bios and I have the latest packages for 12.04 lte
virtinst (0.600.1-1ubuntu3)

Changed in virt-manager (Ubuntu):
status: Expired → New
status: New → Confirmed
status: Confirmed → New
Revision history for this message
Evren Yurtesen (eyurtese-g) wrote :

Please ask if you need more information about this problem... It is strange that it was just closed...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virt-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

What is the output of the "kvm-ok" command if you run it in a terminal?

Changed in virt-manager (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for virt-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in virt-manager (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Trev Peterson (trev-advanced-reality) wrote :

I had this error on 12.04 when I was booted in the xen hypervisor. I added this to my .bashrc:

export VIRSH_DEFAULT_CONNECT_URI=”xen:///”

The problem was then resolved. I found the information here:
https://sanifool.wordpress.com/2012/05/25/installation-of-libvirt-on-xen-for-ubuntu/

I hope this helps others

Revision history for this message
Trev Peterson (trev-advanced-reality) wrote :

Sorry, forgot to mention you will of course need to logout and log back in to reread .bashrc

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.