Re: [libvirt] [PATCH] Introduce yet another migration version in API.

2010-12-15 Thread Eric Blake
On 11/02/2010 07:08 AM, Daniel P. Berrange wrote: Migration just seems togo from bad to worse. We already had to introduce a second migration protocol when adding the QEMU driver, since the one from Xen was insufficiently flexible to cope with passing the data the QEMU driver required.

Re: [libvirt] [PATCH] Introduce yet another migration version in API.

2010-11-09 Thread Chris Lalancette
On 11/02/10 - 01:08:53PM, Daniel P. Berrange wrote: This patch attempts to introduce a version 3 that uses the improved 5 step sequence * Src: Begin - Generate XML to pass to dst - Generate optional cookie to pass to dst * Dst: Prepare - Get ready to

Re: [libvirt] [PATCH] Introduce yet another migration version in API.

2010-11-09 Thread Daniel P. Berrange
On Tue, Nov 09, 2010 at 01:33:50PM -0500, Chris Lalancette wrote: On 11/02/10 - 01:08:53PM, Daniel P. Berrange wrote: This patch attempts to introduce a version 3 that uses the improved 5 step sequence * Src: Begin - Generate XML to pass to dst - Generate

Re: [libvirt] [PATCH] Introduce yet another migration version in API.

2010-11-03 Thread Dan Kenigsberg
On Tue, Nov 02, 2010 at 01:08:53PM +, Daniel P. Berrange wrote: This patch attempts to introduce a version 3 that uses the improved 5 step sequence * Src: Begin - Generate XML to pass to dst - Generate optional cookie to pass to dst * Dst: Prepare

Re: [libvirt] [PATCH] Introduce yet another migration version in API.

2010-11-03 Thread Eric Blake
On 11/02/2010 07:08 AM, Daniel P. Berrange wrote: +static virDomainPtr +virDomainMigrateVersion3 (virDomainPtr domain, + virConnectPtr dconn, + unsigned long flags, + const char *dname, +

[libvirt] [PATCH] Introduce yet another migration version in API.

2010-11-02 Thread Daniel P. Berrange
Migration just seems togo from bad to worse. We already had to introduce a second migration protocol when adding the QEMU driver, since the one from Xen was insufficiently flexible to cope with passing the data the QEMU driver required. It turns out that this protocol still has some flaws that we

Re: [libvirt] [PATCH] Introduce yet another migration version in API.

2010-11-02 Thread Justin Clift
On 11/03/2010 12:08 AM, Daniel P. Berrange wrote: Migration just seems togo from bad to worse. Ahem. Evolving and getting more resilient aren't such a bad thing are they? :) -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] [PATCH] Introduce yet another migration version in API.

2010-11-02 Thread Daniel P. Berrange
On Wed, Nov 03, 2010 at 12:17:22AM +1100, Justin Clift wrote: On 11/03/2010 12:08 AM, Daniel P. Berrange wrote: Migration just seems togo from bad to worse. Ahem. Evolving and getting more resilient aren't such a bad thing are they? :) It has a very big cost in code complexity and the size