From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NuPnU-0000F5-8a for qemu-devel@nongnu.org; Wed, 24 Mar 2010 08:34:56 -0400 Received: from [140.186.70.92] (port=38591 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NuPnS-0000EK-EI for qemu-devel@nongnu.org; Wed, 24 Mar 2010 08:34:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NuPnR-0006La-0y for qemu-devel@nongnu.org; Wed, 24 Mar 2010 08:34:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56216) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NuPnQ-0006LT-Ny for qemu-devel@nongnu.org; Wed, 24 Mar 2010 08:34:52 -0400 Message-ID: <4BAA06E0.5040004@redhat.com> Date: Wed, 24 Mar 2010 14:34:40 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt References: <4BA7C40C.2040505@codemonkey.ws> <4BA91573.9060403@codemonkey.ws> <4BA9A7E1.8080709@redhat.com> <201003241230.58160.paul@codesourcery.com> In-Reply-To: <201003241230.58160.paul@codesourcery.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: "libvir-list@redhat.com" , qemu-devel@nongnu.org On 03/24/2010 02:30 PM, Paul Brook wrote: >> 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. >> > The main blocker to this is converting all the devices to qdev. "partial" > conversions are not sufficient. It's approximately the same problem as a > machine config file. If you have one then the other should be fairly trivial. > Agreed. > IMO the no_user flag is a bug, and should not exist. > Sorry, what's that? -- error compiling committee.c: too many arguments to function