[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] top(1) utility implementation in QEMU
From: |
Fam Zheng |
Subject: |
Re: [Qemu-devel] top(1) utility implementation in QEMU |
Date: |
Tue, 11 Oct 2016 20:51:01 +0800 |
User-agent: |
Mutt/1.7.0 (2016-08-17) |
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