From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: Alexey Eremenko <alexey.eremenko@qumranet.com>,
libvir-list@redhat.com, qemu-devel@nongnu.org,
et-mgmt-tools@redhat.com, kvm@vger.kernel.org
Subject: Re: [libvirt] RE: [Qemu-devel] [ANNOUNCE] virt-mem tools version 0.2.8 released
Date: Thu, 7 Aug 2008 11:47:39 +0100 [thread overview]
Message-ID: <20080807104739.GN32548@redhat.com> (raw)
In-Reply-To: <fdaac4d50808070340g941146emb1f1d8932749120c@mail.gmail.com>
On Thu, Aug 07, 2008 at 07:40:58PM +0900, Jun Koi wrote:
> On Thu, Aug 7, 2008 at 7:20 PM, Alexey Eremenko
> <alexey.eremenko@qumranet.com> wrote:
> >
> > This seems to be great !
> > I think it is similar to OpenVZ concept of controlling VMs from Host, right
> > ?
> >
> > How it works, if it is not installed in guest ?
>
> Basically he does that by inspecting the VM's memory. Something like
> the "instrospection" mechanism.
Yes they peek at the live guest kernel memory image to extract the data.
> One of the problem is that these tools work via libvirt, so on a VM is
> not managed by libvirt, these tools no longer work.
That's not a problem - that's a reason to use libvirt :-) It allows the
same tools to work whether using Xen, QEMU, KVM or any other full machine
virtualization suported by libvirt, rather than being tied to one particular
hypervisor. Not to mention ability to run them remotely, with authentication
and encryption, etc
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 :|
next prev parent reply other threads:[~2008-08-07 10:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 20:00 [Qemu-devel] [ANNOUNCE] virt-mem tools version 0.2.8 released Richard W.M. Jones
2008-08-07 10:20 ` Alexey Eremenko
2008-08-07 10:40 ` [libvirt] " Jun Koi
2008-08-07 10:47 ` Daniel P. Berrange [this message]
2008-08-07 12:55 ` Alexey Eremenko
2008-08-07 12:59 ` Richard W.M. Jones
2008-08-07 13:03 ` Samuel Thibault
2008-08-07 13:06 ` [et-mgmt-tools] " Richard W.M. Jones
2008-08-07 14:30 ` Javier Guerra
2008-08-10 1:28 ` Jamie Lokier
2008-08-10 10:07 ` Richard W.M. Jones
2008-08-10 14:04 ` Richard W.M. Jones
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=20080807104739.GN32548@redhat.com \
--to=berrange@redhat.com \
--cc=alexey.eremenko@qumranet.com \
--cc=et-mgmt-tools@redhat.com \
--cc=junkoi2004@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@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).