I got your point, thanks a lot!
I think the self-build libvirt didn't start, but there is no libvirt-bin under /etc/init.d/, don't know how to start it, and $ initctl start libvirt-bin shows unknow job: libvirt-bin.Thanks a lot!
Best,
Yuanzhen
On Wed, Jul 30, 2014 at 11:30 AM, Eric Blake <eblake@xxxxxxxxxx> wrote:
On 07/30/2014 08:55 AM, Yuanzhen Gu wrote:That's not the actual error message (because the actual message wouldn't
> Hi folks,
>
> I compiled and installed libvirt latest version 1.2.6, based on this
> tutorial,
>
> http://blog.scottlowe.org/2012/11/05/compiling-libvirt-1-0-0-on-ubuntu-12-04-and-12-10/
>
> I have compiled qemu and installed too, and make a symbolic link to
> /usr/bin/qemu-system-x86_64
>
> but my question is even I launch a vm in qemu, $virsh list showed nothing,
> further more,
>
> 1) if I use virtual machine manager, it get connection failiure, due to
> socket to '/var/run/libvirt/libvirt-sock'; No such file of dirctory.
mis-spell directory), but is generally the message you see when libvirtd
is not running. Are you sure you got your self-built libvirtd installed
and running correctly?
I'm not familiar enough with libvirt on ubuntu to know if this is a
>
> 2). there is missing libvirt-bin under /etc/init.d/, after compile and
> installed libvirt 1.2.6
problem. If you are going to replace your distro's old libvirt with a
newer self-built version, it is STILL helpful to install your distro's
libvirt first, to make sure that all the distro-specific tweaks (such as
setting up /etc/init.d/ and so forth to run libvirtd as a daemon) are in
place.
According to the tutorial blog that you linked to, it seems like you
>
> 3). I tried to start libvirtd daemon, sudo /usr/sbin/libvirtd/start
> shows "/usr/sbin/libvirtd: unexpected, non-option, command line
> arguments"
would use 'sudo initctl start libvirt-bin' and not 'sudo
/usr/sbin/libvirtd/start' to start libvirtd - but again, I'm not enough
of an ubuntu user to verify this myself. Again, until you are sure that
your ./configure arguments matched the distro build, and that you have
got libvirtd running correctly, then the rest of your symptoms are
evidence that you didn't install your replacement self-built libvirt
correctly for what the rest of your distro is expecting.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list