HE> patch 1: updated the mof files with the additional "Provider" HE> qualifier. The syntax is "<provider interface>:<module name>". For HE> our providers this means "cmpi:<filename>", HE> e.g. "cmpi:Virt_HostSystem" Ugh.. Is this how OpenWBEM does registration? Meaning, does this eliminate the need for the .registration files for OpenWBEM? I guess by now I should expect no fewer than X different ways of doing things, given X CIMOMs :) HE> patch 2: the registration for OpenWbem requires an entry point HE> <modulename>_Create_InstanceMI, which means that the filename and HE> the providername have to become the same. This is necessary to let HE> STD_InstanceMIStub correctly create the right CMPI entry points. Seems reasonable, and possibly more organized. HE> I have tested this setup with sfcb, Pegasus and OpenWbem and it HE> worked for all. If no one encounteres issues with this slighly HE> changed provider naming, I will create patches for all HE> providers. If someone has a hard requirement to name the provider HE> different compared to the file, please raise your hand ;). I look HE> forward an interesting discussion. The easiest thing would be to go through and rename the providers to match the files, but I wonder if it isn't worth organizing things a bit further. Right now, we have some that are completely expanded (Virt_VirtualSystemManagementService.c) and others that are compressed (Virt_VSSD.c). Would it make sense to also rename the files (where appropriate) for more consistency? -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com