HE> A client request with "assocClass" Xen_ElemenentConformsToProfile HE> and an object path of a KVM_RegisteredProfile is in regard to the HE> mof definition a wrong request. Okay, I understand this issue now, thanks for the clarification. What concerns me about the patch is that we have to change CIM_Foo to Xen_Foo and KVM_Foo, thus doubling the number of association descriptor blocks. Could we not solve this with another match macro or helper function that each handler calls to make sure that the prefix of the reference classname matches that of the assocClass? Such a change would add just another line per handler, instead of an entire std_assoc block for *each* new platform we wish to support. Is there any reason not to solve it this way? -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com