On Mon, Jan 18, 2010 at 10:59:23PM +0100, Matthias Bolte wrote:
> > $ which qemu-system-x86_64
> > /usr/local/bin/qemu-system-x86_64
> > $ ls -l /usr/local/bin/qemu-*
> > -rwxr-xr-x 1 root root 217184 Jan 14 14:00 /usr/local/bin/qemu-img
> > -rwxr-xr-x 1 root root 229120 Jan 14 14:00 /usr/local/bin/qemu-io
> > -rwxr-xr-x 1 root root 210968 Jan 14 14:00 /usr/local/bin/qemu-nbd
> > -rwxr-xr-x 1 root root 2323328 Jan 14 14:01 /usr/local/bin/qemu-system-x86_64
> >
> > This was done by building the qemu-kvm-0.12.1.1 package from source.
> > I am able to run this vm just fine using the qemu-system-x86_64
> > binary. I've tried rebuilding libvirt several times to make it aware
> > that the proper binaries are installed, but it can't seem to find them
> > for some reason.
> >
>
> libvirt expects the QEMU binaries in /usr/bin. e.g. it explicitly
> checks for /usr/bin/qemu-system-x86_64. Try symlinking
> /usr/local/bin/qemu-system-x86_64 to /usr/bin/qemu-system-x86_64.
>
> I'm not sure why the paths are hardcoded instead of using the PATH to
> find the QEMU binaries, like the storage driver does it already:
>
> virFindFileInPath("qemu-img")
We didn't have virFindFileInPath() when we first wrote the QEMU driver.
It is well overdue for us to switch over to using that to detect QEMU
binaries instead of hardcoding /usr/bin. If someone wants to send a
patch, that'd be welcome
Regards,
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