From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NumJK-0000oB-JO for qemu-devel@nongnu.org; Thu, 25 Mar 2010 08:37:18 -0400 Received: from [140.186.70.92] (port=41050 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NumJI-0000mz-PN for qemu-devel@nongnu.org; Thu, 25 Mar 2010 08:37:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NumJH-0006I7-6u for qemu-devel@nongnu.org; Thu, 25 Mar 2010 08:37:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40274) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NumJG-0006I0-Ul for qemu-devel@nongnu.org; Thu, 25 Mar 2010 08:37:15 -0400 Message-ID: <4BAB58F1.20401@redhat.com> Date: Thu, 25 Mar 2010 14:37:05 +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> <20100323145105.GV16253@redhat.com> <4BA8D8A9.7090308@codemonkey.ws> <201003231557.19474.paul@codesourcery.com> <4BA8E6FC.9080207@codemonkey.ws> <4BA901B5.3020704@redhat.com> <4BA9A066.3070904@redhat.com> <20100324103643.GB624@redhat.com> <4BA9EC88.6000906@redhat.com> <20100324134250.38822113@redhat.com> <4BAA6CD9.6060001@redhat.com> <20100324171219.4365318b@redhat.com> <4BAA76EA.2060601@codemonkey.ws> <20100324182501.000b69a7@redhat.com> <4BAA86C2.4020701@codemonkey.ws> <4BAB1E21.8080009@snarc.org> <4BAB5805.9080000@codemonkey.ws> In-Reply-To: <4BAB5805.9080000@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: "libvir-list@redhat.com" , Vincent Hanquez , qemu-devel@nongnu.org, Paul Brook , Luiz Capitulino On 03/25/2010 02:33 PM, Anthony Liguori wrote: >> From my point of view, i wouldn't want to write a high level >> management toolstack in C, specially >> since the API is well defined JSON which is easily available in all >> high level language out there. > > > There's a whole world of C based management toolstacks (CIM). > Gratefully I know very little about CIM, but isn't it language independent? The prominent open source implementation, pegasus, is written in C++. Or are you referring to specific management apps written in C? If they go through CIM, how can they talk qmp? -- error compiling committee.c: too many arguments to function