Kaitlin Rupert wrote:
Dan Smith wrote:
KR> I had troubles compiling with this patch applied - you have an KR> extra open paren here.
Ah, well, I was trying to beat you to the punch. Oh well :)
KR> Also, I was unable to query the CIM_ superclass:
KR> wbemcli ein http://localhost/root/virt:CIM_ResourceAllocationSettingData
KR> Since the classname is not specify, we're unable to get a domain list KR> from the connection.
Hmm, it worked just fine for me because Pegasus translates that into a call of each type. Was this on SFCB perhaps? For class providers sfcb is acting like Pegasus. It translates the CIM_RASD call into a separate provider request for each subclass.
Hmm.. interesting. No, this was with Pegasus. Here's error - I don't see anything strange in the CU_DEBUG output.
[kaitlin@elm3b41 libvirt-cim]$ wbemcli ein http://localhost/root/virt:CIM_ResourceAllocationSettingData * * wbemcli: Cim: (1) CIM_ERR_FAILED: A general error occurred that is not covered by a more specific error code: "Unable to get domain list"
I see the following with ei:
[kaitlin@elm3b41 libvirt-cim]$ wbemcli ei http://localhost/root/virt:CIM_ResourceAllocationSettingData * * wbemcli: Cim: (2) CIM_ERR_ACCESS_DENIED: Access to a CIM resource was not available to the client: "Recursive Use of CIMOMHandle Attempted"
Besides that tiny compilation issue I had no trouble with the provider - neither with sfcb nor with Pegasus. And by reviewing the code I have no idea, where this behavior could come from. For me everything looks fine. What is really strange is, that for nearly the same call two different functions are returning errors: - for the first one (ein) the provider is returning the error - for the second one (ei) the CIMOM is returning the error ... and that error looks like Pegasus is having trouble with calling the same provider for different subclasses Please can you reinstall, restart Pegasus and try again ? What happens ? -- Regards Heidi Eckhart Software Engineer IBM Linux Technology Center - Open Hypervisor