[Libvirt-cim] IMPORTANT: configure Pegasus with "forceProviderProcesses=true"

Dan Smith danms at us.ibm.com
Thu Dec 6 14:28:48 UTC 2007


HE> due to the changes made to the associations (registering the Virt_
HE> provider for each subclass), it is now very important that Pegasus
HE> is configured for "forceProviderProcesses=true". Otherwise only
HE> strange things are happening ...

Can you explain why you think this?  I have
forceProviderProcesses=false and I haven't noticed any weird behavior
thus far (aside from the libvirt init race, which is still not fully
resolved).

There's nothing about the std_association approach that should be any
less thread-safe than the "conventional" approach, other than if
Pegasus itself has issues with multiple calls into the broker at
once.  If this is the case, we should be able to work around it by
preparing additional context objects as you do when you prepare a
thread to run, or we could provide mutual exclusion at the
std_association layer.

Before I could be convinced that we've got a thread-safety issue, I
would want to know what behavior you're seeing, and hear from someone
familiar with the Pegasus internals on why what we're doing is not
safe.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms at us.ibm.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvirt-cim/attachments/20071206/ec9a6cef/attachment.sig>


More information about the Libvirt-cim mailing list