[Qemu-devel] [RFC 0/1] Incoming migration vs early monitor commands

["Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>]

From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>

The attached patch allows you to execute QMP commands from the command
line prior to -incoming or loadvm.

I've hit a few cases where we need to pass some state to an incoming
migration, either:
  1) Before it starts processing data
    e.g. Liang Li's compression patches that have a parameter for the
    number of decompression threads

  2) Before the socket is set up
    so we can influence the connection made; e.g. specify we need to
    have a return path for postcopy, or potentially open multiple connections

For tcp migration you can use the monitor for (1) prior to the accept;
but it's no use for exec or fd.

I'd previously suggested adding option parsing to the -incoming URI; but
then I realised just being able to execute arbitrary QMP commands might
be simpler, and we get reuse of all the migrate capability/parameter
stuff for free, and maybe the arbitrary QMP commands are useful for
something else.

Thoughts?

Dave

Dr. David Alan Gilbert (1):
  Execute arbitrary QMP commands from command line

 include/monitor/monitor.h |  1 +
 monitor.c                 | 41 +++++++++++++++++++++++++++++++++++++++++
 qemu-options.hx           |  9 +++++++++
 vl.c                      | 37 ++++++++++++++++++++++++++++++++++++-
 4 files changed, 87 insertions(+), 1 deletion(-)

-- 
2.1.0