On 06/09/2014 03:49 AM, Chen Fan wrote: > the 'migration_host' description maybe have a bit of difficulty to > understand for user, so add this manual for them. s/maybe have a bit of difficulty/may be a bit difficult/ > > Signed-off-by: Chen Fan <chen.fan.fnst@xxxxxxxxxxxxxx> > --- > tools/virsh.pod | 12 +++++++++++- > 1 file changed, 11 insertions(+), 1 deletion(-) > > diff --git a/tools/virsh.pod b/tools/virsh.pod > index 02671b4..7b30292 100644 > --- a/tools/virsh.pod > +++ b/tools/virsh.pod > @@ -1208,7 +1208,8 @@ such as GFS2 or GPFS. If you are sure the migration is safe or you just do not > care, use I<--unsafe> to force the migration. > > The I<desturi> is the connection URI of the destination host, and > -I<migrateuri> is the migration URI, which usually can be omitted (see below). > +I<migrateuri> is the migration URI for specifying which IP address/URI of the > +destination host to tansfer migration data, which usually can be omitted (see below). s/tansfer/transfer/ Actually, this was rather confusing to me. Would it be better to just simplify this section to instead point to http://libvirt.org/migration.html#uris, rather than trying to rehash that information incompletely? > I<dname> is used for renaming the domain to new name during migration, which > also usually can be omitted. Likewise, I<--xml> B<file> is usually > omitted, but can be used to supply an alternative XML file for use on > @@ -1238,6 +1239,15 @@ seen from the source machine. > > When I<migrateuri> is not specified, libvirt will automatically determine the > hypervisor specific URI, by looking up the target host's configured hostname. > + > +For QEMU/KVM hypervisor, when I<migrateuri> is not specified, at first libvirt > +will ask the destination side whether the optional "migration_host" is specified > +or not, if the "migration_host" is specified, libvirt will use the specified > +network for transferring migration data(the "migrateion_host" is useful when s/migrateion/migration/ > +hosts has multiple network interface). if the "migrateion_host" is not specified and again > +too, libvirt will automatically determine the hypervisor specific URI, by looking > +up the target host's configured hostname. Sounds redundant with the previous paragraph left in place. I'll propose a v3. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list