From nobody Sun May 5 14:10:12 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of redhat.com designates 209.132.183.28 as permitted sender) client-ip=209.132.183.28; envelope-from=libvir-list-bounces@redhat.com; helo=mx1.redhat.com; Authentication-Results: mx.zohomail.com; spf=pass (zoho.com: domain of redhat.com designates 209.132.183.28 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mx.zohomail.com with SMTPS id 1515508476747261.12449771692525; Tue, 9 Jan 2018 06:34:36 -0800 (PST) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2460649023; Tue, 9 Jan 2018 14:34:35 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 77BB9600C9; Tue, 9 Jan 2018 14:34:34 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 95CC118033DA; Tue, 9 Jan 2018 14:34:33 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id w09EX3ax031944 for ; Tue, 9 Jan 2018 09:33:03 -0500 Received: by smtp.corp.redhat.com (Postfix) id 303637F813; Tue, 9 Jan 2018 14:33:03 +0000 (UTC) Received: from eukaryote.localdomain (unknown [10.36.118.47]) by smtp.corp.redhat.com (Postfix) with ESMTP id 24D3E7F80F; Tue, 9 Jan 2018 14:32:58 +0000 (UTC) From: Kashyap Chamarthy To: libvir-list@redhat.com Date: Tue, 9 Jan 2018 15:32:54 +0100 Message-Id: <20180109143254.5184-1-kchamart@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-loop: libvir-list@redhat.com Subject: [libvirt] [PATCH] docs: formatdomain: Specify the default value of 'check' attribute X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 09 Jan 2018 14:34:35 +0000 (UTC) X-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Type: text/plain; charset="utf-8" The 'check' attribute is referring to this: Upstream documentation says, it is: used to request a specific way of checking whether the virtual CPU matches the specification. It is usually safe to omit this attribute when starting a domain and stick with the default value. But doesn't tell *what* the default value is. It is check=3D'partial'. Mention it so. Thanks: Jiri Denemark --- docs/formatdomain.html.in | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index d272cc1ba..8985da836 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -1287,10 +1287,11 @@ attribute can be used to request a specific way of checking whether the virtual CPU matches the specification. It is usually safe to o= mit this attribute when starting a domain and stick with the default - value. Once the domain starts, libvirt will automatically change t= he - check attribute to the best supported value to ensure= the - virtual CPU does not change when the domain is migrated to another - host. The following values can be used: + value (partial>/code>). Once the domain starts, libvirt will + automatically change the check attribute to the best + supported value to ensure the virtual CPU does not change when the + domain is migrated to another host. The following values can be + used: =20
none
@@ -1303,7 +1304,7 @@
partial
Libvirt will check the guest CPU specification before starti= ng a domain, but the rest is left on the hypervisor. It can still - provide a different virtual CPU.
+ provide a different virtual CPU. (This is the default.) =20
full
The virtual CPU created by the hypervisor will be checked --=20 2.13.6 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list