From: "Daniel P. Berrange" <berrange@redhat.com>
To: "陳韋任 (Wei-Ren Chen)" <chenwj@iis.sinica.edu.tw>
Cc: libvirt-users@redhat.com, GaoYi <gaoyi709@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to management KVM virtual machines via libvirt?
Date: Mon, 18 Jun 2012 09:40:59 +0100 [thread overview]
Message-ID: <20120618084058.GF28026@redhat.com> (raw)
In-Reply-To: <20120616120000.GA1566@cs.nctu.edu.tw>
On Sat, Jun 16, 2012 at 08:00:00PM +0800, 陳韋任 (Wei-Ren Chen) wrote:
> CC'ed to libvirt-users.
>
> On Sat, Jun 16, 2012 at 07:00:59PM +0800, GaoYi wrote:
> > Hi all,
> >
> > I am trying to management the VMs created by KVM commandline. However, I
> > found the libvirt cannot connect to the VMs or manage it from virsh. Can
> > anybody provide any help?
> > Best,
>
> Shouldn't this go to libvirt mailing list?
>
> http://libvirt.org/contact.html
There is a way to tell libvirt to attach to an externally
launched KVM process, provided you have configured it with
a monitor socket using the UNIX protocol. This is not always
entirely successful though, due to the sheer number of
different ways QEMU can be launched, which libvirt does not
always understand:
http://berrange.com/posts/2011/07/13/attaching-libvirt-to-an-externally-launched-kvm-instance/
In the long run, I'd really recommend just launch the guests
via libvirt in the first place
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2012-06-18 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 11:00 [Qemu-devel] How to management KVM virtual machines via libvirt? GaoYi
2012-06-16 12:00 ` 陳韋任 (Wei-Ren Chen)
2012-06-18 8:40 ` Daniel P. Berrange [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=20120618084058.GF28026@redhat.com \
--to=berrange@redhat.com \
--cc=chenwj@iis.sinica.edu.tw \
--cc=gaoyi709@gmail.com \
--cc=libvirt-users@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).