On Thu, Oct 09, 2008 at 11:23:16AM -0400, Ben Guthro wrote: > Monitor xenstore for domain changes > NOTE: this patch is currently untested Nice that this is so simple for getting destroy/start events. Its a shame xen doesn't store the paused/crash/etc state here too though. I guess we'll have to try elsewhere if we want to expose that - XenAPI is probably the only viable option there. IIRC XenAPI provided a way to make an XMLRPC call which blocked until a state change event arrived which is the only way to avoid polling with XMLRPC 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 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list