<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> On 03/22/2012 05:40 AM, Shawn Davis wrote: <blockquote cite="mid:CA+_nOodz5JBHvbnpPtNaedrmmYbpgGL7QoLcc5=uFvXsXTg-uA@mail.gmail.com" type="cite"> <div class="gmail_quote">On Wed, Mar 21, 2012 at 4:03 PM, Eric Blake <<a moz-do-not-send="true" href="mailto:eblake@redhat.com">eblake@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">On 03/21/2012 02:58 PM, Shawn Davis wrote: >> Older libvirt had a bug where it wouldn't parse qemu 1.0 version (the >> change from 3 digits to 2 confused the older libvirt). If you're going >> to go with self-built qemu, you might also want to try self-built >> libvirt 0.9.10. >> >> -- >> Eric Blake <a moz-do-not-send="true" href="mailto:eblake@redhat.com">eblake@redhat.com</a> <a moz-do-not-send="true" href="tel:%2B1-919-301-3266" value="+19193013266">+1-919-301-3266</a> >> Libvirt virtualization library <a moz-do-not-send="true" href="http://libvirt.org" target="_blank">http://libvirt.org</a> >> > > I installed libvirt 0.9.10 from source and now virsh is not finding the > following: > > testa@testaT4:~$ virsh list > virsh: /usr/lib/libvirt-qemu.so.0: version `LIBVIRT_QEMU_0.9.4' not found > (required by virsh) </div> Ouch - you've now got version mismatch, where you didn't completely uninstall the distro version, and your self-built version is installed in locations that pick up the distro version. Did you use the right configure flags? <div class="im"> > I can't install qemu 1.0 and libvirt 0.9.10 through apt right? </div> Ah, apt - are you on debian or ubuntu? I don't know as much about the versions that those distros are using (I'm personally using Fedora 16, along with the fedora-virt-preview repo, which gives 0.9.10 pre-built). <div class="im"> > I assume I > had to get them from source. Anyways, please let me know how I can get > virsh to see that I have 0.9.10. Once I get this working and can run that > monitor command I will be in good shape. </div> There might be someone already shipping a pre-built 0.9.10 apt, but I wouldn't know where to tell you to look, so building from source is the other alternative. If you build from libvirt.git, you can use './autobuild.sh --system' to help set the ./configure options that match with the typical installation directories for at least Fedora, but again, I don't know how that fares with the debian installation layout (and patches are welcome to autobuild.sh for anyone that wants to use it on a debian layout). <div class="HOEnZb"> <div class="h5"> -- Eric Blake <a moz-do-not-send="true" href="mailto:eblake@redhat.com">eblake@redhat.com</a> <a moz-do-not-send="true" href="tel:%2B1-919-301-3266" value="+19193013266">+1-919-301-3266</a> Libvirt virtualization library <a moz-do-not-send="true" href="http://libvirt.org" target="_blank">http://libvirt.org</a> </div> </div> </blockquote> </div> Yeah, I am using Ubuntu 11.10. I was able to uninstall the old libvirt and virsh works again but still getting this when trying to start the vm: testa@testaT4:~$ virsh list Id Name State ---------------------------------------------------- testa@testaT4:~$ virsh version Compiled against library: libvir 0.9.10 Using library: libvir 0.9.10 Using API: QEMU 0.9.10 error: failed to get the hypervisor version error: internal error Cannot find suitable emulator for x86_64 testa@testaT4:~$ virsh -c qemu:///system start Shawn error: Failed to connect socket to '/usr/local/var/run/libvirt/libvirt-sock': No such file or directory </blockquote> I guess you're using a old virsh with new libvirt, you may check your virsh command location, if `which virsh` says '/usr/bin/virsh' and `which libvirtd` says /usr/sbin/libvirtd, and socket is /var/run/libvirt/libvirt-sock not above socket path, it's right. It probably your virsh command path is /usr/local/bin/virsh, and your socket path is /var/run/libvirt/libvirt-sock now, if so, you may explicitly specify /usr/bin/virsh or clean up your dirty environment then directly run virsh instead of a absolute path. Good Luck! Alex <blockquote cite="mid:CA+_nOodz5JBHvbnpPtNaedrmmYbpgGL7QoLcc5=uFvXsXTg-uA@mail.gmail.com" type="cite"> error: failed to connect to the hypervisor testa@testaT4:~$ Thanks again for helping me out! <pre wrap=""> <fieldset class="mimeAttachmentHeader"></fieldset> _______________________________________________ libvirt-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:libvirt-users@redhat.com">libvirt-users@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/libvirt-users">https://www.redhat.com/mailman/listinfo/libvirt-users</a></pre> </blockquote> </body> </html>