From: Eric Blake <eblake@redhat.com>
To: Yuanzhen Gu <yg185@cs.rutgers.edu>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] can't connect hypervisor after compile and installed latest libvirt 1.2.6
Date: Wed, 30 Jul 2014 09:19:43 -0600 [thread overview]
Message-ID: <53D90D0F.3070901@redhat.com> (raw)
In-Reply-To: <CAOjERXzqbbQ1g6A+EjwHcOH1m0DkaUYPJH2aNwQGeKq8OR6Jog@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On 07/30/2014 09:15 AM, Yuanzhen Gu wrote:
> Good morning,
>
> I compiled and installed libvirt latest version 1.2.6,
> I have compiled qemu and installed too, and make a symbolic link to
> /usr/bin/qemu-system-x86_64
This sounds like a question better directed to libvirt-users@redhat.com.
>
> 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.
Usually, that's a sign of you not compiling your self-built version with
the same configure options as the pre-compiled version available from
your distro, coupled with mismatched files. Nothing at all to do with
qemu. When asking on the libvirt list, make sure to mention your distro
and the set of options you passed to ./configure when self-building.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
prev parent reply other threads:[~2014-07-30 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 15:15 [Qemu-devel] can't connect hypervisor after compile and installed latest libvirt 1.2.6 Yuanzhen Gu
2014-07-30 15:19 ` Eric Blake [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53D90D0F.3070901@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yg185@cs.rutgers.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).