From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=56416 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PsOJh-000255-Dp
	for qemu-devel@nongnu.org; Wed, 23 Feb 2011 18:40:22 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1PsOJe-00027C-QC
	for qemu-devel@nongnu.org; Wed, 23 Feb 2011 18:40:19 -0500
Received: from mx1.redhat.com ([209.132.183.28]:38817)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1PsOJe-000276-I0
	for qemu-devel@nongnu.org; Wed, 23 Feb 2011 18:40:18 -0500
From: Juan Quintela <quintela@redhat.com>
In-Reply-To: <4D65945A.3090106@codemonkey.ws> (Anthony Liguori's message of
	"Wed, 23 Feb 2011 17:12:26 -0600")
References: <1298497114-7436-1-git-send-email-aliguori@us.ibm.com>
	<m3d3mi2w76.fsf@trasno.org> <4D65945A.3090106@codemonkey.ws>
Date: Thu, 24 Feb 2011 00:38:48 +0100
Message-ID: <m3zkpm1fuf.fsf@trasno.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Qemu-devel] Re: [PATCH] Split machine creation from the main loop
Reply-To: quintela@redhat.com
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: qemu-devel@nongnu.org

Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 02/23/2011 05:00 PM, Juan Quintela wrote:
>> Anthony Liguori<aliguori@us.ibm.com>  wrote:
>>    
>>> The goal is to enable the monitor to run independently of whether the machine
>>> has been created such that the monitor can be used to specify all of the
>>> parameters for machine initialization.
>>>
>>> Signed-off-by: Anthony Liguori<aliguori@us.ibm.com>
>>>      
>> I agree that it is one step in the right direction, but we are still
>> calling qemu_machine_init() before calling the main_loop().
>>
>> What is the plan from here?
>>    
>
> 1) Decouple QMP from qemu_machine_init().  This really requires the
> introduction of the new QAPI server that exists outside of the chardev
> infrastructure since chardevs are currently initialized in
> qemu_machine_init().
>
> 2) Make qemu_machine_init() take no parameters and just reference
> global state.

Any good idea how that global state is going to be stored?

I just want to be able to launch a qemu on a different machine and
migrate the "configuration" to it, for doing that, I really need what
values are different from default or anything like that.  So as you can
see, I am very interested on that work.

Later, Juan.