From: Avi Kivity <avi@redhat.com>
To: Jonathan Petersson <jonathan.petersson@op5.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: RAM utilization issues
Date: Thu, 12 Jan 2012 15:41:42 +0200 [thread overview]
Message-ID: <4F0EE316.6030606@redhat.com> (raw)
In-Reply-To: <CAKM0yO8ELS0svJzDeRpk=RotW-CnvnDGsNMZRUwTY6CXbDp8jw@mail.gmail.com>
On 01/12/2012 02:56 PM, Jonathan Petersson wrote:
> It seams that our provider hasn't built a management engine for
> ballooning, however I found this project
> (https://github.com/aglitke/mom) which is compatible with libvirt
> however as the mangement-engine we use doesn't utilize libvirt it's
> not compatible, would you happen to know of a different project that
> utilizes qemu-socket.
>
>
No, sorry. In general it's hard to have multiple management tools
talking to a single guest because of the need for synchronization.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-01-12 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 9:27 RAM utilization issues Jonathan Petersson
2012-01-12 10:36 ` Avi Kivity
2012-01-12 10:47 ` Jonathan Petersson
2012-01-12 10:51 ` Avi Kivity
2012-01-12 12:56 ` Jonathan Petersson
2012-01-12 13:41 ` Avi Kivity [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=4F0EE316.6030606@redhat.com \
--to=avi@redhat.com \
--cc=jonathan.petersson@op5.com \
--cc=kvm@vger.kernel.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