Kaitlin Rupert wrote:
Heidi Eckhart wrote:
The only problem I encountered was with a non existing instance, e.g. a typo in the InstanceID as below. Therefore the provider segfaults. Please can you have a look into this ? Thanks.
wbemcli gi 'http://localhost/root/virt:Xen_AllocationCapabilities.InstanceID="ProcessorPol/0"'
Thanks Heidi for testing this. Are you testing on sfcb? Yes, testing on sfcb. I tested this same scenario on Pegasus (before submitting), and I got the following error:
* * wbemcli: Cim: (6) CIM_ERR_NOT_FOUND: The requested object could not be found *
Well, yet another difference between Pegasus and sfcb. Pegasus seems to take the given object path, do an enumerateInstanceNames and iterate through the returned instances trying to find the requested one. This error_not_found is definitely created by Pegasus itself, while the getInstance() of our provider does not get called in this case. On the other hand sfcb directs this call to the provider (that's why he can call himself "small footprint" ;) ).
I just tried applying these patches on a clean tree and re-testing - I get the same error. I'm testing with tog-pegasus-2.6.1-2.fc8.
Has anyone else encountered a segfault or other unexpected error condition?
I will have a look into it and try to find out where it segfault. -- Regards Heidi Eckhart Software Engineer Linux Technology Center - Open Hypervisor heidieck@linux.vnet.ibm.com ************************************************** IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschaeftsfuehrung: Herbert Kircher Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294