From 9b521dbc0891767add23d57af6acd7ef721a917c Mon Sep 17 00:00:00 2001 From: Jiri Denemark Date: Tue, 14 Feb 2017 23:32:24 +0100 Subject: [PATCH] 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 --- docs/formatdomain.html.in | 10 ---------- 1 file changed, 10 deletions(-) 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. - - In both host-model and host-passthrough - mode, the real (approximate in host-passthrough mode) CPU - definition which would be used on current host can be determined by - specifying VIR_DOMAIN_XML_UPDATE_CPU flag when calling - virDomainGetXMLDesc 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 - custom mode for more robust migration.
model
-- GitLab