KR> Applying these patches didn't fix the dups for me (btw, thanks for
KR> finding the dups!). I think the Virt_ provider still gets called
KR> twice.
Yeah, with more testing, I still get dups as well. Changing back to a
unified provider name doesn't change the fact that the CIMOM still
calls the provider once per registered class. The unified case
prevents us from having a key to filter on too.
My previous statement about connect_by_classname() is invalid too,
because we use the ref for connecting, which will be, for example,
Xen_Foo in both cases (for the KVM instance and the Xen instance of
the provider's registration).
So, I think the bottom line is: We still need ASSOC_MATCH() and it is
the proper way to fix this problem for the associations that we
currently have without it.
Right?
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com