From: Jiri Denemark <jdenemar@redhat.com>
Date: Tue, 14 Feb 2017 22:32:24 +0000 (+0100)
Subject: docs: Drop obsolete statement about CPU modes and migration
X-Git-Tag: CVE-2017-2635~20
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9b521dbc0891767add23d57af6acd7ef721a917c;p=thirdparty%2Flibvirt.git

docs: Drop obsolete statement about CPU modes and migration

The guest CPU definition has always been updated automatically during
migration. And currently we just transform any host-model CPU into a
custom one when a domain starts.

Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
---

diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index b69bd4c44c..249d91f31d 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -1307,16 +1307,6 @@
           a migration is attempted then the guest may hang or crash upon
           resuming execution on the destination host.</dd>
         </dl>
-
-        In both <code>host-model</code> and <code>host-passthrough</code>
-        mode, the real (approximate in <code>host-passthrough</code> mode) CPU
-        definition which would be used on current host can be determined by
-        specifying <code>VIR_DOMAIN_XML_UPDATE_CPU</code> flag when calling
-        <code>virDomainGetXMLDesc</code> API. When running a guest that might
-        be prone to operating system reactivation when presented with
-        different hardware, and which will be migrated between hosts with
-        different capabilities, you can use this output to rewrite XML to the
-        <code>custom</code> mode for more robust migration.
       </dd>
 
       <dt><code>model</code></dt>