Bug 507437 - virt-manager does not find a default connection to kvm/qemu
Summary: virt-manager does not find a default connection to kvm/qemu
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-22 18:34 UTC by Eric Paris
Modified: 2009-12-14 21:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-02 09:43:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Fix qemu autodetection at app startup (597 bytes, text/plain)
2009-06-29 17:49 UTC, Cole Robinson
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1285 0 normal SHIPPED_LIVE virt-manager enhancement and bug fix update 2009-09-01 09:51:32 UTC

Description Eric Paris 2009-06-22 18:34:48 UTC
Description of problem:

kvm-83-77.el5
python-virtinst-0.400.3-4.el5
libvirt-0.6.3-11.el5
virt-manager-0.6.1-4.el5

Starting virt-manager has no default automagic connection.

ln -s /usr/libexec/qemu-kvm /usr/bin

Problem goes away.

Comment 1 Cole Robinson 2009-06-29 17:49:08 UTC
Created attachment 349833 [details]
Fix qemu autodetection at app startup

The proper way to do this would be to teach virt-manager to handle an a uri of 'None', which will defer to libvirt for this detection. Unfortunately, this change looks to be a wee bit involved, so I think it is safer to just try and look into /usr/libexec for the qemu-kvm binary, similar to how the existing detection works.

Comment 6 Cole Robinson 2009-07-07 18:27:07 UTC
Built into virt-manager-0.6.1-6.el5. Setting to MODIFIED.

Comment 12 errata-xmlrpc 2009-09-02 09:43:45 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1285.html


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