From: Alon Levy <alevy@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: airlied@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] make screendump an async command
Date: Fri, 14 Jun 2013 14:07:19 -0400 (EDT) [thread overview]
Message-ID: <196559746.19701897.1371233239366.JavaMail.root@redhat.com> (raw)
In-Reply-To: <336668023.19700685.1371232970391.JavaMail.root@redhat.com>
> > Hi,
> >
> > > Note: due to QAPI not generating async commands yet I had to remove the
> > > schema screendump definition.
> >
> > Hmm, that will break libvirt I suspect. Guess this one has to wait
> > until QAPI gained proper async command support.
>
> It doesn't break anything. I've tested,
To clarify, I tested with "virsh screenshot" as well.
> and here is the QMP transcript, the
> only difference is internal to qemu, from libvirt point of view it issues
> the same command and gets the same response:
>
> $ ./x86_64-softmmu/qemu-system-x86_64 -qmp stdio
> {"QMP": {"version": {"qemu": {"micro": 50, "minor": 5, "major": 1},
> "package": ""}, "capabilities": []}}
> {"execute":"qmp_capabilities"}
> {"return": {}}
> {"execute":"screendump","arguments":{"filename":"test2.ppm"}}
> {"return": {}}
>
>
> >
> > cheers,
> > Gerd
> >
> >
> >
> >
>
>
next prev parent reply other threads:[~2013-06-14 18:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 19:27 [Qemu-devel] [PATCH] make screendump an async command Alon Levy
2013-06-13 20:08 ` Paolo Bonzini
2013-06-13 20:35 ` Alon Levy
2013-06-14 11:18 ` Gerd Hoffmann
2013-06-14 18:02 ` Alon Levy
2013-06-14 18:07 ` Alon Levy [this message]
2013-06-14 18:21 ` Anthony Liguori
2013-06-14 23:55 ` Alon Levy
2013-06-17 13:41 ` Luiz Capitulino
2013-06-17 6:06 ` Gerd Hoffmann
2013-06-17 9:30 ` Alon Levy
2013-06-17 14:00 ` Gerd Hoffmann
2013-06-17 13:54 ` Luiz Capitulino
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=196559746.19701897.1371233239366.JavaMail.root@redhat.com \
--to=alevy@redhat.com \
--cc=airlied@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kraxel@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).