On Mon, Dec 07, 2015 at 02:14:11PM +0800, Fam Zheng wrote:
> On Mon, 12/07 13:56, Peter Xu wrote:
> > + if (runstate_check(RUN_STATE_INMIGRATE)) {
> > + error_setg(errp, "Dump not allowed during incoming migration.");
> > + return;
> > + }
> > +
>
> Detached dump when "inmigrate" is disabled, that's OK. But what about sync
> dump? It used to be possible, but now is disabled. Just asking to make sure
> this is the intention rather than oversight.
That's my intention here. This should be an idea from one of Paolo's
review comment (forgot which one) and I hope I did not miss
anything. I took this since I failed to find a use case that user
might dump guest memory during incoming migration.
Thanks.
Peter
>
> Fam
