From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=48813 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OP0jM-0006WD-8Y
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 18:05:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <quintela@redhat.com>) id 1OP0jK-000846-PI
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 18:05:08 -0400
Received: from mx1.redhat.com ([209.132.183.28]:59337)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <quintela@redhat.com>) id 1OP0jK-00083q-Ih
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 18:05:06 -0400
From: Juan Quintela <quintela@redhat.com>
In-Reply-To: <4C190760.9070605@codemonkey.ws> (Anthony Liguori's message of
	"Wed, 16 Jun 2010 12:18:24 -0500")
References: <1276619430-15871-1-git-send-email-aliguori@us.ibm.com>
	<1276619430-15871-7-git-send-email-aliguori@us.ibm.com>
	<m3631jnmv7.fsf@trasno.mitica> <20100616162544.GS13996@redhat.com>
	<4C190760.9070605@codemonkey.ws>
Date: Thu, 17 Jun 2010 00:05:00 +0200
Message-ID: <m3typ2r5v7.fsf@trasno.mitica>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Qemu-devel] Re: [CFR 6/10] cont command
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Anthony Liguori <aliguori@us.ibm.com>, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>, qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>, Luiz Capitulino <lcapitulino@redhat.com>

Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 06/16/2010 11:25 AM, Daniel P. Berrange wrote:
>>
>>> This is related to the commands, not QMP per se:
>>>
>>> Once that we are talking about "cont" command.  There are two cases that
>>> we need to think of:
>>>
>>> - incoming migration:
>>>
>>> If you start with -incoming foo, and then run "cont" on the monitor
>>> without having started the migration .... corruption is ensured.
>>>      
>> This is why '-incoming' command line arg should die, and be replaced
>> with a 'incoming' monitor command that would simply not allow 'cont'
>> to be run until it completed.
>>
>> For that matter, even with '-incoming' arg on command line we could
>> refuse to honour 'cont' until the incoming migration had been done.
>>    
>
> If we had an incoming migration command, I think we'd have to think
> careful about it's semantics.  Is it reasonable to allow a machine
> that's otherwise running to do an incoming command?

It is the same problem that loadvm.

And no, loadvm several times don't work well either.

Later, Juan.