Bug 1288699 - libvirtError: internal error Cannot find suitable emulator for x86_64
Summary: libvirtError: internal error Cannot find suitable emulator for x86_64
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 23
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-05 08:41 UTC by amit
Modified: 2015-12-07 10:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-05 17:51:13 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Machine details (3.71 KB, text/plain)
2015-12-05 08:41 UTC, amit 		no flags Details
View All

Description amit 2015-12-05 08:41:00 UTC 
Created attachment 1102503 [details]
Machine details

Hi,

I'm using Fedora 20 and when I run virt-manager command on root user I get the below error message,

Unable to connect to libvirt.

internal error: Cannot find suitable emulator for x86_64

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1118, in _open_notify
    logging.debug("conn version=%s", self._backend.conn_version())
  File "/usr/share/virt-manager/virtinst/connection.py", line 291, in conn_version
    self._conn_version = self._libvirtconn.getVersion()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3677, in getVersion
    if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self)
libvirtError: internal error: Cannot find suitable emulator for x86_64

I attached laptop info, should I need to move with Fedora 21 or 22?
Comment 1 amit 2015-12-05 08:42:33 UTC 
If anybody know why this produce error then I would like to work on this bug.

Thanks
Amit G
Comment 2 Cole Robinson 2015-12-05 17:51:13 UTC 
Fedora 20 and 21 are both end-of-life now and not supported. So step #1 is updating to fedora 23 and see if it reproduces there. If so, please reopen
Comment 3 amit 2015-12-07 10:13:26 UTC 
On Fedora 23 it works fine.

Thanks,
Amit G
Note You need to log in before you can comment on or make changes to this bug.