On Thu, 28 Sep 2017 12:02:35 +0200 Kevin Wolf <kw...@redhat.com> wrote:
> Am 28.09.2017 um 01:05 hat Jan Dakinevich geschrieben: > > > OK but if it's useful as an hmp command, why not as a qmp command? > > > > The command is designed for debugging and produces quite sightly output. For > > respective qmp command most of `info virtio' output would excessive and > > unneccesary. > > The general policy is that HMP commands should only call QMP command > implementations internally rather than doing things themselves, to make > sure that a management tool can achieve everything the monitor provides > with QMP and doesn't have to fall back to parsing HMP output. > > If we are certain that this feature is useless for automated use and > nobody will ever want to use it in scripts (sounds like a bold claim to > me), maybe an exception can be justified. I think this is up to the > monitor maintainers. Having a way to get at things like virtio status might be useful (for example, noticing if a device has NEEDS_RESET set).
