From: Fam Zheng <famz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: prashanth sunder <prashanth.sunder@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] top(1) utility implementation in QEMU
Date: Tue, 11 Oct 2016 20:51:01 +0800 [thread overview]
Message-ID: <20161011125101.GG5814@lemon> (raw)
In-Reply-To: <87k2doimqu.fsf@dusky.pond.sub.org>
On Tue, 10/04 09:42, Markus Armbruster wrote:
> >> What's the advantage over simply using another QMP monitor? Naturally,
> >> injecting arbitrary QMP commands behind libvirt's back isn't going to
> >> end well, but "don't do that then". Information queries and listening
> >> to events should be safe.
> >
> > In order to avoid a Libvirt "tainted" state at production env, of course
> > assuming qemu-top is useful there at all.
>
> Adding another QMP-like protocol seems like a rather steep price just
> for avoiding "tainted".
>
> Any chance we can provide this feature together with libvirt instead of
> behind its back?
That would be the best, but I am not sure how to make an appropriate interface.
>
> >> Note that we could have a QMP command to spawn monitors. Fun!
> >
> > Cool, and how hard is it to implement a QMP command to kill monitors? :)
>
> For spawning, we need to adapt the current spawn code to work after
> initial startup, too. For killing, we need to write new code. Might be
> harder, but can't say until we try.
>
Fam
next prev parent reply other threads:[~2016-10-11 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 13:44 [Qemu-devel] top(1) utility implementation in QEMU prashanth sunder
2016-09-26 16:28 ` Daniel P. Berrange
2016-09-29 2:45 ` Fam Zheng
2016-09-30 17:08 ` Markus Armbruster
2016-10-01 12:12 ` Fam Zheng
2016-10-04 7:42 ` Markus Armbruster
2016-10-11 12:51 ` Fam Zheng [this message]
2016-10-11 13:09 ` Daniel P. Berrange
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=20161011125101.GG5814@lemon \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=prashanth.sunder@gmail.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).