qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC v5 00/26] QMP: out-of-band (OOB) execution support


From: Dr. David Alan Gilbert
Subject: Re: [Qemu-devel] [RFC v5 00/26] QMP: out-of-band (OOB) execution support
Date: Fri, 15 Dec 2017 11:43:18 +0000
User-agent: Mutt/1.9.1 (2017-09-22)

* Fam Zheng (address@hidden) wrote:
> On Tue, 12/05 13:51, Peter Xu wrote:
> > This version is mostly document update, and dropped the single patch
> > that is migration related (will be put into postcopy recovery
> > series).
> 
> Sorry if I'm asking an already answered question, if so please remind me with
> some pointers..
> 
> Can we completely hide the "OOB" concept from QMP to avoid the interface
> complication? In other words, the new "migrate-recover" command can be
> implemented in a way that it always try to run out of band as if it has
> "run-oob=true", without user specifying it or even negotiating it.
> 
> Because it seems "migrate-recover" is only useful with "run-oob=true".
> 
> Of course without introducing the whole OOB concept in QMP, what this command
> does will sound very hacky, but the bahavior can be documented just well on 
> the
> single command. I don't see a big advantage in generalizing OOB at the QMP 
> level
> so far. Do we have a list of other commands to be made OOB?

Many of the status commands can be converted to OOB, and the important
thing is that the management layer can tell whether OOB can tell which
commands are OOBable.

Dave

> Fam
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK



reply via email to

[Prev in Thread] Current Thread [Next in Thread]