On Tue, Oct 28, 2008 at 02:00:48PM -0400, Ben Guthro wrote: Indeed - looking at the code in xen which fires this event, I see no way to determine which is the new/old domain. This does appear to be the only option, it doesn't mean that we need to make Xen a fully stateful driver like QEMU. All this really amounts to is tracking a list of integer IDs or UUIDs - this is small enough that we can just keep track of it in the 'struct _xenUnifiedPrivate' which is per-virConnectPtr instance. When we get a introduceDomain watch, we'd just need to re-query for the list of IDs and compare to figure out what's new/old. We only need do this tracking if we've got a domain event callback registered, so I think this is acceptable. 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 :|