Re: [libvirt] [PATCH v3 1/3] libxl: add p2p migration

2016-02-04 Thread Jim Fehlig
On 02/03/2016 12:36 PM, Joao Martins wrote: > > On 02/02/2016 11:41 PM, Jim Fehlig wrote: >> Also, if the connection dies, how are we informed about that? >> Would that be done via the connect close callback that was removed in this >> version? It is not clear to me how errors on the dconn

Re: [libvirt] [PATCH v3 1/3] libxl: add p2p migration

2016-02-03 Thread Joao Martins
On 02/02/2016 11:41 PM, Jim Fehlig wrote: > Joao Martins wrote: >> Introduce support for VIR_MIGRATE_PEER2PEER in libvirt migration. >> Most of the changes occur at the source and no modifications >> at the receiver. >> >> In P2P mode there is only the Perform phase so we must handle >> the

Re: [libvirt] [PATCH v3 1/3] libxl: add p2p migration

2016-02-02 Thread Jim Fehlig
Joao Martins wrote: > Introduce support for VIR_MIGRATE_PEER2PEER in libvirt migration. > Most of the changes occur at the source and no modifications > at the receiver. > > In P2P mode there is only the Perform phase so we must handle > the connection with the destination and actually perform

Re: [libvirt] [PATCH v3 1/3] libxl: add p2p migration

2016-02-01 Thread Jim Fehlig
On 01/20/2016 12:00 PM, Joao Martins wrote: > Introduce support for VIR_MIGRATE_PEER2PEER in libvirt migration. > Most of the changes occur at the source and no modifications > at the receiver. > > In P2P mode there is only the Perform phase so we must handle > the connection with the destination

[libvirt] [PATCH v3 1/3] libxl: add p2p migration

2016-01-20 Thread Joao Martins
Introduce support for VIR_MIGRATE_PEER2PEER in libvirt migration. Most of the changes occur at the source and no modifications at the receiver. In P2P mode there is only the Perform phase so we must handle the connection with the destination and actually perform the migration.