From nobody Mon Feb 9 00:53:48 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) client-ip=170.10.129.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1641322511; cv=none; d=zohomail.com; s=zohoarc; b=kx7lobtRwvMr3rfD9xHmR/abMRE8Gjd+YRSDVimn7Y3WdM3gaLtnmKgmrprJuZGUPWxOkzmVFsY9Tix8KBmVY1lZ94tNzXSsjt8zWMC/UblI0fIPYyqZ02eT8/OgpFDkr/+efrcLQOssOLHm9VyZsz/QHugAna3yp/9gtgaHMkQ= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1641322511; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=FpqqSm39SPsL8BUcBBpPyB61QT8JrXgeDhnjbCapAuI=; b=WDJmXaHDSeWU6+fODn8K5+bR14iYLDJw/wL5Luwo2pnHHiPAbpO8aSNVfJ4iUip0CVdo8tRP2AbcvhuTc14aOkVI5Fn9IEye03UQkTFIWzm/Xi01b5AbI7BuUb7/um81yqLYpjQjEi+b2JUs8Ys1gDeYBKa2x9pQ17j9EYKfP54= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com with SMTPS id 164132251194881.05278660238503; Tue, 4 Jan 2022 10:55:11 -0800 (PST) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-605-BnUvndNCOOyyVpyuWBfAbg-1; Tue, 04 Jan 2022 13:55:07 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9BFD66123E; Tue, 4 Jan 2022 18:55:01 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7C11978A14; Tue, 4 Jan 2022 18:55:01 +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 4B26C4A7CA; Tue, 4 Jan 2022 18:55:01 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 204IsxXP013333 for ; Tue, 4 Jan 2022 13:54:59 -0500 Received: by smtp.corp.redhat.com (Postfix) id AF0F334D53; Tue, 4 Jan 2022 18:54:59 +0000 (UTC) Received: from kinshicho.usersys.redhat.com (unknown [10.40.193.201]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B146434D41; Tue, 4 Jan 2022 18:54:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1641322510; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=FpqqSm39SPsL8BUcBBpPyB61QT8JrXgeDhnjbCapAuI=; b=AqSZH2Snxsqmd3Wv40UeRLwj54kl8oq/kpY/NQF3SmeEWmc3WB47goO4anlqZ0YIKu533b PeB20gVt8ItSZgmfWhbI0LB3z1b7Ji32n3BdQFMD6OCsM1xTH3+gyZQQwPBBqb9OruGEMb wsi3AsL0rouaX14lVd8DQaay6JEIagM= X-MC-Unique: BnUvndNCOOyyVpyuWBfAbg-1 From: Andrea Bolognani To: libvir-list@redhat.com Subject: [libvirt PATCH 14/17] docs: Note hvf support for domain elements Date: Tue, 4 Jan 2022 19:52:53 +0100 Message-Id: <20220104185256.339072-15-abologna@redhat.com> In-Reply-To: <20220104185256.339072-1-abologna@redhat.com> References: <20220104185256.339072-1-abologna@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-loop: libvir-list@redhat.com Cc: r.bolshakov@yadro.com 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: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1641322513447100001 Content-Type: text/plain; charset="utf-8" From: Roman Bolshakov Many domain elements have "QEMU and KVM only" or "QEMU/KVM since x.y.z" remarks. Most of the elements work for HVF domain, so it makes sense to add respective notices for HVF domain. All the elements have been manually tested. Signed-off-by: Roman Bolshakov Signed-off-by: Andrea Bolognani --- docs/formatdomain.rst | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst index 3e9de05249..e27fb23119 100644 --- a/docs/formatdomain.rst +++ b/docs/formatdomain.rst @@ -1426,7 +1426,8 @@ In case no restrictions need to be put on CPU model a= nd its features, a simpler :since:`Since 7.1.0` with the QEMU driver. =20 Both ``host-model`` and ``host-passthrough`` modes make sense when a do= main - can run directly on the host CPUs (for example, domains with type ``kvm= ``). + can run directly on the host CPUs (for example, domains with type ``kvm= `` + or ``hvf``). The actual host CPU is irrelevant for domains with emulated virtual CPUs (such as domains with type ``qemu``). However, for backward compatibili= ty ``host-model`` may be implemented even for domains running on emulated = CPUs @@ -1750,7 +1751,7 @@ Each of these states allow for the same four possible= actions. The domain will be terminated and then restarted with a new name. (Only supported by the libxl hypervisor driver.) =20 -QEMU/KVM supports the ``on_poweroff`` and ``on_reboot`` events handling the +QEMU/KVM/HVF supports the ``on_poweroff`` and ``on_reboot`` events handlin= g the ``destroy`` and ``restart`` actions, but the combination of ``on_poweroff`= ` set to ``restart`` and ``on_reboot`` set to ``destroy`` is forbidden. =20 @@ -1885,8 +1886,8 @@ are: Physical address extension mode allows 32-bit guests to address more th= an 4 GB of memory. ``acpi`` - ACPI is useful for power management, for example, with KVM guests it is - required for graceful shutdown to work. + ACPI is useful for power management, for example, with KVM or HVF guest= s it + is required for graceful shutdown to work. ``apic`` APIC allows the use of programmable IRQ management. :since:`Since 0.10.2 (QEMU only)` there is an optional attribute ``eoi`` with values ``on`` = and @@ -6195,14 +6196,16 @@ A video device. =20 You can provide the amount of video memory in kibibytes (blocks of 1024 bytes) using ``vram``. This is supported only for guest type of "vz", "= qemu", - "vbox", "vmx" and "xen". If no value is provided the default is used. I= f the + "kvm", "hvf", "vbox", "vmx" and "xen". + If no value is provided the default is used. If the size is not a power of two it will be rounded to closest one. =20 The number of screen can be set using ``heads``. This is supported only= for - guests type of "vz", "kvm", "vbox" and "vmx". + guests type of "vz", "kvm", "hvf", "vbox" and "vmx". =20 - For guest type of "kvm" or "qemu" and model type "qxl" there are option= al - attributes. Attribute ``ram`` ( :since:`since 1.0.2` ) specifies the si= ze of + For guest type of "kvm", "hvf" or "qemu" and model type "qxl" there are + optional attributes. + Attribute ``ram`` ( :since:`since 1.0.2` ) specifies the size of the primary bar, while the attribute ``vram`` specifies the secondary b= ar size. If ``ram`` or ``vram`` are not supplied a default value is used. = The ``ram`` should also be rounded to power of two as ``vram``. There is al= so --=20 2.31.1