Guys thanks a lot for taking the time out to reply, Although adding the $PATH & symbolic link methods both solved the "No hypervisor found" error on virt-manager but when I try to create a VM using the wizard it says: "No hypervisor options were found for this connection" "This usually means that QEMU or KVM is not installed on your machine, or the KVM modules are not loaded." The QEMU I want to connect to libvirt has no KVM kernel drivers (DPDK Qemu). There is a single binary "qemu-system-x86_64" I am using virt-manager GUI to see whether qemu is being detected by libvirt or not (is there a better/CLI method?) On 5 March 2014 15:51, Daniel P. Berrange <berrange@redhat.com> wrote:
On Tue, Mar 04, 2014 at 02:09:19PM -0700, Eric Blake wrote:
On 03/04/2014 05:12 AM, Asadullah Hussain wrote:
Hello I have manually compiled a customized qemu (1.4.0) which runs fine on its own (create VM etc) but I want to access this qemu through libvirt (virt-manager, virsh etc).
But the libvirt driver only looks into "/usr/bin" for qemu binaries, how can I tell libvirt to connect to my qemu which is placed at "/home/user/qemu" directory.
Libvirt only looks into precompiled locations (default to /usr/bin) if you fail to specify an explicit location; but you can force libvirt to use your version of qemu by specifying the <emulator> element under <devices> in your domain XML.
Actually we will search through $PATH for QEMU binaries, so if you install somewhere unusual, just make sure libvirtd sees an updated $PATH env variable including the new location.
Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/:| |: http://libvirt.org -o- http://virt-manager.org:| |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc:|
-- Asadullah Hussain