On Mon, Jul 23, 2007 at 11:00:21AM +0100, Richard W.M. Jones wrote: > >step virDrvDomainMigrateFinish() might be needed, it could for example > >resume on the target side and also verify the domain is actually okay. > >That could improve error handling and feels a lot more like a transactional > >system where you really want an atomic work/fail operation and nothing > >else. > > Yes. It's important to note that the internals may be changed later, > although that may complicate things if we want to allow people to run > incompatible versions of the daemons. [Another email on that subject is > coming up after this one]. We need to treat the binary on-the-wire ABI for the client<->daemon the same way as our public ELF library ABI. Never break it, only add to it. So if we think the internals client<->server needs may change we should avoid including this code in a release until we're more satisfied with its longevity. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 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