le network interface). if the "migrateion_host" is not
> specified
> +too, libvirt will automatically determine the hypervisor specific URI, by
> looking
> +up the target host's configured hostname.
> +
> There are a few scenarios where specifying I may help:
>
> =over 4
> --
> 1.9.3
--
Yasunori Goto
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
> On Fri, 2014-06-06 at 15:57 +0900, Yasunori Goto wrote:
> > Chen-san,
> >
> > > ping...
> >
> > I suppose it seems to be difficult for users to understand...
> > I think following order of description is desirable.
> >
> > - What
> > case
> > I should be explicitly specified, using an IP address
> > associated
> > -with the network to be used.
> > +with the network to be used. In particular, Some hypervisors could be easy
> > to
> > +specify the default network interface by setting 'migration_host'. then the
> > +I can be omitted.
> >
> > =item * The firewall restricts what ports are available. When libvirt
> > generates
> > a migration URI, it will pick a port number using hypervisor specific
> > rules.
>
--
Yasunori Goto
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
