On Thu, May 14, 2009 at 06:43:10PM -0700, Noah Zoschke wrote:
Hello,
I have been playing around with the libvirt domain event handlers in Python and am seeing something surprising. I am using trunk libvirt and `event-test.py` with some more of the debugging strings uncommented.
When I trigger my first event:
[snip]
So my handler is always one event behind.
This behavior is not intended is it? Am I missing either something in `event-test.py` or in how I am using virsh that would correct this behavior?
This is not intended behaviour. I have verified that I see the same problem when running the event-test.py demo program. The C based example event-test.c does work correctly. So either this is a bug in the python demo program, or a bug in the python APIs for events. Not sure which yet... Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|