qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-ga command listing
Date: Wed, 02 Jan 2013 14:26:21 -0700	[thread overview]
Message-ID: <50E4A5FD.8040806@redhat.com> (raw)
In-Reply-To: <20130102203424.GB2289@jefflaptop.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

On 01/02/2013 01:34 PM, Jeff Cody wrote:
> On Mon, Dec 31, 2012 at 01:41:57PM -0700, Eric Blake wrote:
>> Is there a guest-agent command for querying the list of available
>> commands for a given guest agent?  If not, should there be?  In other
>> words, I'm looking for the counterpart to QMP {"execute":"query-commands"}.
>>
> 
> Hi Eric,
> 
> There is guest-info ({"execute": "guest-info"}), which returns a list
> of supported commands, and whether or not that command is enabled or
> disabled (e.g. it may be blacklisted).  Here is an example of the
> output, with guest-file-* operations blacklisted (formatted slightly
> for better readability):
> 
> {"return": 
>     {"version": "1.0", "supported_commands": 
>         [{"enabled": true, "name": "guest-network-get-interfaces"}, 

Thanks, that's mostly what I wanted.  Still missing is the ability to
tell if a command is expected to return a value on success, though.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

      reply	other threads:[~2013-01-02 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-31 20:41 [Qemu-devel] qemu-ga command listing Eric Blake
2013-01-02 20:34 ` Jeff Cody
2013-01-02 21:26   ` Eric Blake [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=50E4A5FD.8040806@redhat.com \
    --to=eblake@redhat.com \
    --cc=jcody@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).