From nobody Tue Dec 16 16:56:26 2025 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of lists.libvirt.org designates 8.43.85.245 as permitted sender) client-ip=8.43.85.245; envelope-from=devel-bounces@lists.libvirt.org; helo=lists.libvirt.org; Authentication-Results: mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of lists.libvirt.org designates 8.43.85.245 as permitted sender) smtp.mailfrom=devel-bounces@lists.libvirt.org; dmarc=fail(p=none dis=none) header.from=redhat.com Return-Path: Received: from lists.libvirt.org (lists.libvirt.org [8.43.85.245]) by mx.zohomail.com with SMTPS id 1740065259776598.0829845335489; Thu, 20 Feb 2025 07:27:39 -0800 (PST) Received: by lists.libvirt.org (Postfix, from userid 996) id A5A571F67; Thu, 20 Feb 2025 10:27:38 -0500 (EST) Received: from lists.libvirt.org (localhost [IPv6:::1]) by lists.libvirt.org (Postfix) with ESMTP id 4631D217B; Thu, 20 Feb 2025 10:26:35 -0500 (EST) Received: by lists.libvirt.org (Postfix, from userid 996) id 4FA712160; Thu, 20 Feb 2025 10:26:31 -0500 (EST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.libvirt.org (Postfix) with ESMTPS id 32CCA217A for ; Thu, 20 Feb 2025 10:26:25 -0500 (EST) Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-142-oWgHOqFuObClBvU6d1Hd1Q-1; Thu, 20 Feb 2025 10:26:23 -0500 Received: from mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id BF4E81800876 for ; Thu, 20 Feb 2025 15:26:22 +0000 (UTC) Received: from orkuz (unknown [10.43.3.115]) by mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 4B3671956094 for ; Thu, 20 Feb 2025 15:26:22 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on lists.libvirt.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,RCVD_IN_VALIDITY_RPBL_BLOCKED, RCVD_IN_VALIDITY_SAFE_BLOCKED,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1740065184; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=oM1oUomDucAf1yBP0blnLzquCoMrmIs9TUcyuMag+yw=; b=D5D56PEWq1PpbC5CIYU7B2X/4bl6HjDv/Xkoi2Mb8L1ncLYFSodm/LBiI+HfZA+EyTPsQr nZRwo5W6WyMjZRFZShJyKBhK62ZtjmwU++Vje2v2naw4a+lHGuYHbjcF2FmVuRjagV6NJR rDTeyVcw0/pipZwAerAfTs8iF1pKInU= X-MC-Unique: oWgHOqFuObClBvU6d1Hd1Q-1 X-Mimecast-MFC-AGG-ID: oWgHOqFuObClBvU6d1Hd1Q_1740065182 From: Jiri Denemark To: devel@lists.libvirt.org Subject: [PATCH 02/13] docs: Clarify documentation of virsh hypervisor-cpu-baseline Date: Thu, 20 Feb 2025 16:26:04 +0100 Message-ID: <3fdc2152f64a922d29db6e6f68d274805a6cde44.1740064957.git.jdenemar@redhat.com> In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.15 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: x-IAp-FmQZsEZ1JqstnUR6EmfMeloKqQ4DBHuPdQIP4_1740065182 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable Message-ID-Hash: WPQJSGYLCAZ6RGOCKDE6VYDSEQVWP3SG X-Message-ID-Hash: WPQJSGYLCAZ6RGOCKDE6VYDSEQVWP3SG X-MailFrom: jdenemar@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-config-1; header-match-config-2; header-match-config-3; header-match-devel.lists.libvirt.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.2.2 Precedence: list List-Id: Development discussions about the libvirt library & tools Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-ZohoMail-DKIM: fail (Header signature does not verify) X-ZM-MESSAGEID: 1740065262048019100 Content-Type: text/plain; charset="utf-8" Using host CPU definition with hypervisor-cpu-baseline is possible, but it provide incorrect results and thus it should not be documented the same way we describe the correct usage. Also using host-model CPU from domain capabilities was not described clearly enough. Signed-off-by: Jiri Denemark --- docs/manpages/virsh.rst | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-) diff --git a/docs/manpages/virsh.rst b/docs/manpages/virsh.rst index 63ad619eab..06c2802b3f 100644 --- a/docs/manpages/virsh.rst +++ b/docs/manpages/virsh.rst @@ -1000,15 +1000,19 @@ As an alternative for *FILE* in case the XML would = only contain a CPU model with no additional features the CPU model name itself can be passed as *mo= del*. Exactly one of *FILE* and *model* must be used. =20 -The XML *FILE* may contain either host or guest CPU definitions describing= the -host CPU model. The host CPU definition is the element and its conte= nts -as printed by ``capabilities`` command. The guest CPU definition may be cr= eated -from the host CPU model found in domain capabilities XML (printed by -``domcapabilities`` command). In addition to the elements, this comm= and -accepts full capabilities XMLs, or domain capabilities XMLs containing the= CPU -definitions. It is recommended to use only the CPU definitions from domain -capabilities, as on some architectures using the host CPU definition may e= ither -fail or provide unexpected results. +The XML *FILE* should contain guest CPU definitions created from the host = CPU +model found in the ```` element domain capabilit= ies +XMLs (printed by the ``domcapabilities`` command on each host). The +```` elements themselves or even their ```` +parent elements found in domain capabilities XMLs are not accepted. The +elements have to be transformed into actual CPU definitions. + +Alternatively this command will automatically extract the CPU definitions = when +provided with domain capabilities XMLs. + +For historical reasons the XML *FILE* may also contain host CPU definition= s, +but such usage is strongly discouraged as it will most likely provide inco= rrect +results. =20 When *FILE* contains only a single CPU definition, the command will print = the same CPU with restrictions imposed by the capabilities of the hypervisor. --=20 2.48.1