On Wed, Oct 07, 2009 at 03:09:17PM +0200, Paolo Bonzini wrote: > > > Sounds fine by me, but I wonder about the change of semantic for > > client server not at the same version level. Could you explain what > >might happen in those case ? > > Here is the result of my testing (source libvirtd is always new): This is why you're missing the ABI incompatability problems. The perform() RPC call that you changed is invoked against the source libvirtd. So a mis-matched version for client vs source libvirt will get a RPC error. 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 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list