The result of ein AllocationCapabilites is correct: wbemcli ein http://root:password@localhost:5988/root/virt:Xen_AllocationCapabilities localhost:5988/root/virt:Xen_AllocationCapabilities.InstanceID="ProcessorPool/0" localhost:5988/root/virt:Xen_AllocationCapabilities.InstanceID="MemoryPool/0" localhost:5988/root/virt:Xen_AllocationCapabilities.InstanceID="DiskPool/foo" localhost:5988/root/virt:Xen_AllocationCapabilities.InstanceID="NetworkPool/xenbr0" localhost:5988/root/virt:Xen_AllocationCapabilities.InstanceID="NetworkPool/virbr0" But failing qurey of gi AllocationCapabilities: wbemcli gi http://root:password@localhost:5988/root/virt:Xen_AllocationCapabilities.... * * wbemcli: Cim: (1) CIM_ERR_FAILED: A general error occurred that is not covered by a more specific error code: "Could not get ResourceType." * Below is part of Virt_AllocationCapabilities provider's code: static CMPIStatus GetInstance(CMPIInstanceMI *self, const CMPIContext *context, const CMPIResult *results, const CMPIObjectPath *reference, const char **properties) { return return_alloc_cap(reference, results, 0); } static CMPIStatus EnumInstanceNames(CMPIInstanceMI *self, const CMPIContext *context, const CMPIResult *results, const CMPIObjectPath *reference) { return alloc_cap_instances(_BROKER, reference, results, true, NULL); } I think the causing issue it the same as Xen_EnabledLogicalElementCapabilities provider. Thanks! Best, Regards Daisy Guo Lian Yun E-mail: yunguol(a)cn.ibm.com IBM China Development Lab, Shanghai, China TEL: (86)-21-61008057