Hide Forgot
virt-manager uses the default dbus timeout (25 seconds) for installing packages libvirt+kvm when the app is first run. 25s isn't enough time, so we should bump the timeout. Fixed upstream here: http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=ca5bd0de0addfbfbbe0f3da8bca33d563292d08f To reproduce: yum remove -y libvirt qemu\* as a regular user, delete all connections from virt-manager, restart the app virt-manager asks to install libvirt/kvm. say yes wait at the root password prompt for 25 seconds, virt-manager will throw an error (though packagekit keeps on going) the error: DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Fixed in virt-manager-0.9.0-2.el6
this bug can reproduce with : virt-manager-0.8.6-4.el6 verify with: virt-manager-0.9.0-5.el6 step: 1: run command line #yum remove -y libvirt qemu\* 2: delete all connections from virt-manager 3: run command line #virt-manager --debug 4: ask to install libvirt/kvm. click yes after 25 seconds, no error message shown up,no error message in debug info, install will successful. Verification passed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1642.html