From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-guest-agent question
Date: Wed, 21 Oct 2015 10:28:53 -0500 [thread overview]
Message-ID: <20151021152853.18764.34766@loki> (raw)
In-Reply-To: <20151021151040.10420.91322@loki>
Quoting Michael Roth (2015-10-21 10:10:40)
> Quoting Vasiliy Tolstov (2015-10-19 08:41:35)
> > I'm try to understand sources of qga and have a question- does agent
> > execute commands synchronous or if i'm send firstly long running
> > command and after that send short lived command, short lived command
> > response can be sended before first command result?
> > Thanks!
>
> Yes, commands are executed asynchronously. guest-exec kicks them off and
> returns a handle. guest-exec-status can be called later with that handle
> to check on the status of the command. If the command has completed,
> guest-exec-status will report the return status, along with stdout/stderr
> if capture mode was enabled. Multiple commands can be issued/running at
> any one time.
>
> The documentation in qemu.git/qga/qapi-schema.json has more exact details.
I assumed you were referring to 'commands' via the recent
guest-exec command that was added, but in case that's not what you were
asking about:
The guest agent commands themselves are synchronous, and qga will
process and respond to requests as it recieves them, one at a time,
from start to finish.
>
> >
> > --
> > Vasiliy Tolstov,
> > e-mail: v.tolstov@selfip.ru
> >
next prev parent reply other threads:[~2015-10-21 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 13:41 [Qemu-devel] qemu-guest-agent question Vasiliy Tolstov
2015-10-21 15:10 ` Michael Roth
2015-10-21 15:28 ` Michael Roth [this message]
2015-10-24 0:29 ` Vasiliy Tolstov
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=20151021152853.18764.34766@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=v.tolstov@selfip.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.