On 07/20/10 - 11:53:43AM, Daniel P. Berrange wrote:
> On Fri, Jul 16, 2010 at 09:38:10AM -0400, Chris Lalancette wrote:
> > If you try to execute two concurrent migrations p2p
> > from A->B and B->A, the two libvirtd's will deadlock
> > trying to perform the migrations. The reason for this is
> >
On Fri, Jul 16, 2010 at 09:38:10AM -0400, Chris Lalancette wrote:
> If you try to execute two concurrent migrations p2p
> from A->B and B->A, the two libvirtd's will deadlock
> trying to perform the migrations. The reason for this is
> that in p2p migration, the libvirtd's are responsible for
> ma
On 07/16/10 - 09:38:10AM, Chris Lalancette wrote:
> If you try to execute two concurrent migrations p2p
> from A->B and B->A, the two libvirtd's will deadlock
> trying to perform the migrations. The reason for this is
> that in p2p migration, the libvirtd's are responsible for
> making the RPC Pre
If you try to execute two concurrent migrations p2p
from A->B and B->A, the two libvirtd's will deadlock
trying to perform the migrations. The reason for this is
that in p2p migration, the libvirtd's are responsible for
making the RPC Prepare, Migrate, and Finish calls. However,
they are currentl
