On Fri, Sep 01, 2017 at 10:08:18AM +0100, Daniel P. Berrange wrote:
> IIUC, you are trying to make it possible to register multiple event
> loop impls. This is *not* supported usage of libvirt. You must
> call 'virEventRegisterImpl' before opening any connection, and once
> called you are forbidden to call it again.
Yes, that's correct. Can't I do it, even after I close all the connections?
Why then libvirt_virEventRegisterImpl (libvirt-python/libvirt-override.c:5434)
seems to accomodate for running it second time?
The reason for this is we have separate event loop for each test case, but the
whole suite runs in a single process. The Impl has to use the new loop for
each test. Would it be better to just substitute the loop in a long-lived Impl
instance?
--
pozdrawiam / best regards _.-._
Wojtek Porczyk .-^' '^-.
Invisible Things Lab |'-.-^-.-'|
| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>
Attachment:
signature.asc
Description: Digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
