Description of problem: On my local laptop that runs F20, I have one VM created via virt-manager on the local connection. I have another connection, to a RHEL6-based host, which has several VMs. When I click 'new' to create a VM in the RHEL6 connection, virt-manager correctly uses /usr/libexec/qemu-kvm as the path to the binary. In the same virt-manager session, if I create a new VM in the local connection, it again tries to use /usr/libexec/qemu-kvm, and fails, as on Fedora, the binary path is /usr/bin/qemu-kvm. This reproduces the other way too: create a new VM on the local connection, and then attempt to create one on the remote connection, and the remote connection attempts to use /usr/bin/qemu-kvm.
Thanks for the report Amit, fixed upstream now: commit 1cf8b629909ebbfb3caee235d03c7e9bb149091e Author: Cole Robinson <crobinso> Date: Wed Mar 12 11:37:36 2014 -0400 create: Invalidate cached caps across similar connections (bz 1075444)
*** Bug 1076155 has been marked as a duplicate of this bug. ***
virt-manager-1.0.1-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/virt-manager-1.0.1-1.fc20
Package virt-manager-1.0.1-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing virt-manager-1.0.1-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-4273/virt-manager-1.0.1-1.fc20 then log in and leave karma (feedback).
virt-manager-1.0.1-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.