[libvirt] [Qemu-devel] Re: Supporting hypervisor specific APIs in libvirt
Avi Kivity
avi at redhat.com
Thu Mar 25 13:48:57 UTC 2010
On 03/25/2010 03:44 PM, Anthony Liguori wrote:
> On 03/25/2010 07:37 AM, Avi Kivity wrote:
>> 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++.
>
> There is also SFCB which is written in C.
Ok.
>
> But an awful lot of the providers for pegasus are written in C.
But we're concerned with only one, the virt provider. None of the
others will use libqemu?
> The point is, C is a lowest common denominator and it's important to
> support in a proper way.
Problem is, it means horrible support for everyone else.
--
error compiling committee.c: too many arguments to function
More information about the libvir-list
mailing list