On Mon, Nov 23, 2009 at 11:09:28AM -0500, Cole Robinson wrote: > On 11/23/2009 01:43 AM, Dustin Xiong wrote: > > Date: Fri, 20 Nov 2009 08:14:09 -0500, cole wrote: > >> > >> cc-ing libvirt-list > >> > > >> >>> My cpu is itanium 64, the OS is RHEL.The libvirt is 0.6.3, > > virt-manager > >> >>> is 0.6.1. > >> > >> Ah, are you using the version of libvirt that comes with RHEL 5.4? That > >> version has been patched to only look for the qemu-kvm binary in one > >> spot: /usr/libexec/qemu-kvm IIRC. You could try to work with that! , but > >> since you are already building upstream KVM, vir! t-manage r, and > > virtinst, > >> might not be a bad idea to pull upstream libvirt as well. > >> > > > > yes, my libvirt rpm and other related rpms all came from the RHEL 5.4 > > iso. And they all build for itanium 64 > > # rpm -qa | grep libvirt > > libvirt-python-0.6.3-20.el5 > > libvirt-devel-0.6.3-20.el5 > > libvirt-0.6.3-20.el5 > > > > And i try to make a link, it still doesn't work. > > ln -s /usr/local/bin/qemu-system-ia64 /usr/libexec/qemu-system-ia64 > > > > Actually I think that destination needs to be /usr/libexec/qemu-kvm, not > qemu-system-ia64. And looking at the rhel5 code, this can also be > /usr/bin/qemu-kvm That's not going to help. 'ia64' is not listed as a valid architecture in qemu_conf.c, so it'll never be pulled into the capabilities, and thus libvirt will never even look for a KVM binary Someone needs to update qemu_conf.c to handle ia64 correctly. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list