qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Puneet Bakshi <bakshi.puneet@gmail.com>,
	libvir-list@redhat.com, qemu-devel@nongnu.org,
	qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] [libvirt] Not able to run "virsh qemu-agent-command" when socat is working
Date: Wed, 02 Jul 2014 10:39:02 -0600	[thread overview]
Message-ID: <53B435A6.9000605@redhat.com> (raw)
In-Reply-To: <CALBPQ31-DnKfMzmJshaGqYM2o7tUJYmh-1s091DzUC86SgZ+xA@mail.gmail.com>

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

On 07/02/2014 01:13 AM, Puneet Bakshi wrote:
> Hi,
> 
> I am running qemu guest agent in Windows 2k8. I am able to execute
> "qemu-agent-commands" using socat but not through "virsh
> qemu-agent-command".
> 

> *Host CentOS system*
> 
> socat returns response appropriately.
>     [root@sdsr720-14 ~]# echo "{'execute':'guest-ping'}" | socat
> stdio,ignoreeof /var/lib/libvirt/qemu/g06.agent
>     {"return": {}}

Note your spelling...

> 
> *"virsh qemu-agent-command" returns blank.*
> 
>     [root@sdsr720-14 ~]# virsh qemu-agent-command vm_win_06 '{ "execute":
> "guest_ping"}'

and compare it to here.  There is no guest_ping command, only
guest-ping.  It's a bug in libvirt that guest-agent-command doesn't
output a useful error message when attempting to run a non-existing
command, but you'll never hit that bug if you pass valid commands to the
agent in the first place.

-- 
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: 604 bytes --]

  reply	other threads:[~2014-07-02 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  7:13 [Qemu-devel] Not able to run "virsh qemu-agent-command" when socat is working Puneet Bakshi
2014-07-02 16:39 ` Eric Blake [this message]
2014-07-05 17:53   ` [Qemu-devel] [libvirt] " Puneet Bakshi

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=53B435A6.9000605@redhat.com \
    --to=eblake@redhat.com \
    --cc=bakshi.puneet@gmail.com \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@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).