From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NuJTO-0006ff-SM
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 01:49:46 -0400
Received: from [140.186.70.92] (port=41191 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NuJTN-0006fX-6c
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 01:49:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1NuJTL-0005jB-Ey
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 01:49:45 -0400
Received: from mx1.redhat.com ([209.132.183.28]:36631)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1NuJTL-0005ir-7N
	for qemu-devel@nongnu.org; Wed, 24 Mar 2010 01:49:43 -0400
Message-ID: <4BA9A7E1.8080709@redhat.com>
Date: Wed, 24 Mar 2010 07:49:21 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs
	in libvirt
References: <4BA7C40C.2040505@codemonkey.ws>	<20100323145105.GV16253@redhat.com>	<4BA8D8A9.7090308@codemonkey.ws>	<201003231557.19474.paul@codesourcery.com>	<4BA8E6FC.9080207@codemonkey.ws>
	<20100323180747.GM364@redhat.com> <4BA91573.9060403@codemonkey.ws>
In-Reply-To: <4BA91573.9060403@codemonkey.ws>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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.gnu.org/pipermail/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: "libvir-list@redhat.com" <libvir-list@redhat.com>, Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org

On 03/23/2010 09:24 PM, Anthony Liguori wrote:
>
> We also provide an API for guest creation (the qemu command line).


As an aside, I'd like to see all command line options have qmp 
equivalents (most of them can be implemented with a 'set' command that 
writes qdev values).  This allows a uniform way to control a guest, 
whether at startup or runtime.  You start with a case, cold-plug a 
motherboard, cpus, memory, disk controllers, and power it on.

I would also like a way to read the entire qdev tree from qmp.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.