qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: libvir-list@redhat.com, mprivozn@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/1] qemu-ga: add guest-sync-delimited
Date: Mon, 6 Feb 2012 18:48:28 -0600	[thread overview]
Message-ID: <20120207004828.GA14061@illuin> (raw)
In-Reply-To: <1328573255-13410-1-git-send-email-mdroth@linux.vnet.ibm.com>

On Mon, Feb 06, 2012 at 06:07:34PM -0600, Michael Roth wrote:
> Sorry for the somewhat redundant cover letter, but needed to note that:
> 
> This applies on top of "[PATCH v2 0/8] qemu-ga: add support for Windows", and
> can also be obtained from:
> git://github.com/mdroth/qemu.git qga-guest-sync-delimited
> 
> As noted in the commit there's a wiki write-up with more details on what
> exactly this is for:
> 
> http://wiki.qemu.org/Features/QAPI/GuestAgent#QEMU_Guest_Agent_Protocol
> 
> It's not absolutely required, but it does make dealing with some communication
> corner cases a heck of a lot easier.
> 

Actually, let me re-spin this without the deprecated flag for
guest-sync, since I suspect a more common client implementation would do
something like:

qga.write(obj_to_json_string(req_obj))
resp_obj = obj_from_json_string(qga.readline())

as opposed to the JSON streamer that qemu-ga/QMP uses. You might miss a
response doing the above approach if there was garbage in the channel,
but you'll always been able to recover on the second attempt. So
guest-sync is still useful there, assuming we codify 1-line-per-response
in the QGA protocol.

      parent reply	other threads:[~2012-02-07  0:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07  0:07 [Qemu-devel] [PATCH 0/1] qemu-ga: add guest-sync-delimited Michael Roth
2012-02-07  0:07 ` [Qemu-devel] [PATCH] " Michael Roth
2012-02-07 15:09   ` Daniel P. Berrange
2012-02-07  0:48 ` Michael Roth [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=20120207004828.GA14061@illuin \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=libvir-list@redhat.com \
    --cc=mprivozn@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).