commit 95094d69b16b952255de97325a2ae70722aa5700
Author: W. David Ashley <w.david.ashley(a)gmail.com>
Date: Sun Jul 5 11:21:29 2015 -0500
Domains Chapter
Migration section
-added attitional parameter information for thr migrate and migrateToURI methods.
en-US/Guest_Domains.xml | 35 ++++++++++++++++++++++++++++++++++-
1 files changed, 34 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Guest_Domains.xml b/en-US/Guest_Domains.xml
index ee411e9..b633cf9 100644
--- a/en-US/Guest_Domains.xml
+++ b/en-US/Guest_Domains.xml
@@ -657,6 +657,35 @@
complete successfully, storage needs to be shared between the source and
target hypervisors.
</para>
<para>
+ The first parameter of the <literal>migrate</literal> method
specifies the connectiion to be used to the
+ target of the migration. This parameter is required.
+ </para>
+ <para>
+ The second parameter of the <literal>migrate</literal> method
specifies a set of flags that control how the
+ migration takes place over the connection. If npo flags are needed then the
parameter should
+ be set to zero.
+ </para>
+ <para>
+ The third parameter of the <literal>migrate</literal> method
specifies a new name for the domain on the target
+ of the migration. Not all hypervisors support this operation. If no rename of
the domain is
+ required then the parameter shoule be set to
<literal>None</literal>.
+ </para>
+ <para>
+ The third parameter of the <literal>migrate</literal> method
specifies a new name for the domain on the target
+ of the migration. Not all hypervisors support this operation. If no rename of
the domain is
+ required then the parameter can be set to
<literal>None</literal>.
+ </para>
+ <para>
+ The forth parameter of the <literal>migrate</literal> method
specifies the URI to be used as the
+ target of the migration. A URI is only required when the target system
supports multiple
+ hypervisors. If ther is only a single hypervisor on the target system then
+ the parameter can be set to <literal>None</literal>.
+ </para>
+ <para>
+ The fifth and last parameter of the <literal>migrate</literal>
method specifies the bandwidth in
+ MiB/s to be used. If this maximum is not needed then set the parameter to
zero.
+ </para>
+ <para>
To migrate a guest domain to a connection that is already open use the
<literal>migrate</literal>
method. An example follows:
</para>
@@ -665,6 +694,10 @@
<programlisting language="Python"><xi:include
href="extras/Domains-Example-22.py" parse="text"
xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
</example>
<para>
+ The <literal>migrateToURI</literal> method similar except that
the destination URI is the first
+ parameter instead of an existing connection.
+ </para>
+ <para>
To migrate a guest domain to a URI use the
<literal>migrateToURI</literal>
method. An example follows:
</para>
@@ -674,7 +707,7 @@
</example>
<para>
To migrate a live guest domain to a URI use the
<literal>migrate</literal> or the
- <literal>migrateToURI</literal> with the
<literal>VIR_MIGRATE_LIVE</literal>. An example follows:
+ <literal>migrateToURI</literal> with the
<literal>VIR_MIGRATE_LIVE</literal> flag set. An example follows:
</para>
<example>
<title>Migrate a Domain to an Open Connection</title>