On Thu, 2016-08-25 at 11:41 -0400, Daniel P. Berrange wrote:
>
> I think where the confusion is coming is that libvirt will work in
> two different ways with P2P migration. If the TUNNELLED flag is set,
> then the migration data will go over the Libvirtd <-> libvirtd
> connection, which is
On Thu, Aug 25, 2016 at 12:01:40PM +0200, Alberto Planas Dominguez wrote:
> On Wed, 2016-08-24 at 11:18 -0400, Daniel P. Berrange wrote:
> > On Wed, Aug 24, 2016 at 05:07:50PM +0200, Alberto Planas Dominguez
> > wrote:
>
> Daniel, thanks for the fast reply!!
>
> > > Unfortunately was closed as
On Wed, 2016-08-24 at 11:18 -0400, Daniel P. Berrange wrote:
> On Wed, Aug 24, 2016 at 05:07:50PM +0200, Alberto Planas Dominguez
> wrote:
Daniel, thanks for the fast reply!!
> > Unfortunately was closed as invalid, and the solution provided is
> > completely unrelated. The solution suggested is
On Wed, Aug 24, 2016 at 05:07:50PM +0200, Alberto Planas Dominguez wrote:
> Unfortunately was closed as invalid, and the solution provided is
> completely unrelated. The solution suggested is based on
> `live_migration_inbound_addr`, that is related with the libvirtd URI,
> not the qmeu one. I
Hi!
I have a question about live migration in a p2p scenario. We have a
deployment where the compute nodes have several interfaces. The
hostname is associate with one of them, that is used for nova to do all
the communication, and also the live migration.
The thing is that we want to use the
