From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: amit.shah@redhat.com, liang.z.li@intel.com,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC 1/1] Execute arbitrary QMP commands from command line
Date: Thu, 29 Jan 2015 16:28:15 +0000 [thread overview]
Message-ID: <20150129162815.GG2391@work-vm> (raw)
In-Reply-To: <54CA594E.5030605@redhat.com>
* Eric Blake (eblake@redhat.com) wrote:
> On 01/29/2015 08:54 AM, Dr. David Alan Gilbert wrote:
> >> The idea of a QMP command to trigger incoming migration looks
> >> reasonable. We can probably use a qapi union for a nicer syntax,
> >> something like:
> >>
> >> {"execute": "migrate-incoming", "arguments": {
> >> "type": "tcp", "port": 44 } }
> >> vs.
> >> {"execute": "migrate-incoming", "arguments": {
> >> "type": "fd", "fd": 0 } }
> >> vs.
> >> {"execute": "migrate-incoming", "arguments": {
> >> "type": "exec", "command": [ "cat", "/path/to/file" ] } }
> >>
> >> and so forth.
> >
> > Compared to just taking a URI argument that Dan suggested, that's quite a
> > bit of rework to do the reworking of each transport which is pretty
> > trivial.
>
> Yes, but getting the interface right means that adding future extensions
> will be easier, with less string parsing hacks.
I guess so, but I still have to maintain the -incoming string interface
and an HMP equivalent of whatever we come up with here.
So what would the .args_type look like in qmp-commands.hx; something like this?
.args-type = "type:s,port:-i,host:-s,command:-s"
Dave
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-01-29 16:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 15:06 [Qemu-devel] [RFC 0/1] Incoming migration vs early monitor commands Dr. David Alan Gilbert (git)
2015-01-29 15:06 ` [Qemu-devel] [RFC 1/1] Execute arbitrary QMP commands from command line Dr. David Alan Gilbert (git)
2015-01-29 15:15 ` Daniel P. Berrange
2015-01-29 15:21 ` Eric Blake
2015-01-29 15:54 ` Dr. David Alan Gilbert
2015-01-29 16:01 ` Eric Blake
2015-01-29 16:28 ` Dr. David Alan Gilbert [this message]
2015-01-29 17:45 ` Eric Blake
2015-01-29 20:21 ` Dr. David Alan Gilbert
2015-01-29 20:48 ` Eric Blake
2015-01-30 9:38 ` Dr. David Alan Gilbert
2015-01-30 9:50 ` Paolo Bonzini
2015-01-30 9:56 ` Dr. David Alan Gilbert
2015-02-03 10:12 ` Amit Shah
2015-02-03 11:02 ` Paolo Bonzini
2015-01-30 9:50 ` Daniel P. Berrange
2015-01-30 8:34 ` Markus Armbruster
2015-01-30 9:20 ` Dr. David Alan Gilbert
2015-01-30 9:43 ` Markus Armbruster
2015-01-30 8:35 ` Markus Armbruster
2015-01-29 15:22 ` Dr. David Alan Gilbert
2015-01-29 15:31 ` Daniel P. Berrange
2015-01-29 15:46 ` Dr. David Alan Gilbert
2015-01-29 15:50 ` Eric Blake
2015-01-29 15:56 ` Dr. David Alan Gilbert
2015-01-29 15:58 ` Daniel P. Berrange
2015-01-30 9:52 ` Paolo Bonzini
2015-01-30 10:02 ` Dr. David Alan Gilbert
2015-01-30 10:27 ` Paolo Bonzini
2015-01-29 15:25 ` [Qemu-devel] [RFC 0/1] Incoming migration vs early monitor commands Eric Blake
2015-01-29 23:08 ` Paolo Bonzini
2015-01-30 9:42 ` Dr. David Alan Gilbert
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=20150129162815.GG2391@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=eblake@redhat.com \
--cc=liang.z.li@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).