From nobody Mon Feb 9 10:54:38 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of redhat.com designates 209.132.183.37 as permitted sender) client-ip=209.132.183.37; envelope-from=libvir-list-bounces@redhat.com; helo=mx5-phx2.redhat.com; Authentication-Results: mx.zoho.com; spf=pass (zoho.com: domain of redhat.com designates 209.132.183.37 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; Return-Path: Received: from mx5-phx2.redhat.com (mx5-phx2.redhat.com [209.132.183.37]) by mx.zohomail.com with SMTPS id 148638410946717.721485334647582; Mon, 6 Feb 2017 04:28:29 -0800 (PST) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by mx5-phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v16CLhl5062928; Mon, 6 Feb 2017 07:21:43 -0500 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id v16CLNlS017577 for ; Mon, 6 Feb 2017 07:21:23 -0500 Received: from beluga.usersys.redhat.com (dhcp129-94.brq.redhat.com [10.34.129.94]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v16CL6xK013739; Mon, 6 Feb 2017 07:21:22 -0500 From: Erik Skultety To: libvir-list@redhat.com Date: Mon, 6 Feb 2017 13:19:58 +0100 Message-Id: <6d0a6f7f9b24b14fea45da8f9ae8e47c181930d4.1486383339.git.eskultet@redhat.com> In-Reply-To: References: In-Reply-To: References: X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 X-loop: libvir-list@redhat.com Cc: Erik Skultety Subject: [libvirt] [PATCH 16/16] docs: Document the new hostdev device type 'mdev' 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-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Type: text/plain; charset="utf-8" Signed-off-by: Erik Skultety --- docs/formatdomain.html.in | 40 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 36 insertions(+), 4 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 77d8e71..10cef31 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -3765,6 +3765,20 @@ </devices> ... =20 +

or:

+ +
+  ...
+  <devices>
+    <hostdev mode=3D'subsystem' type=3D'mdev'>
+    <source>
+      <address domain=3D'0x0000' bus=3D'0x06' slot=3D'0x02' function=3D=
'0x0'/>
+      <uuid>c2177883-f1bb-47f0-914d-32a22e3a8804</uuid>
+    </source>
+    </hostdev>
+  </devices>
+  ...
+
hostdev
The hostdev element is the main container for descr= ibing @@ -3809,12 +3823,20 @@ type passes all LUNs presented by a single HBA to the guest.
+
mdev
+
For mediated devices (Since 3.1.0) + the managed attribute controls whether the mediated + device to be assigned is pre-created by the user or shall be cre= ated + automatically by libvirt using the information provided by the + source element. Currently, only the value "no" is + supported which is the same as omitting the attribute completely. +

- Note: The managed attribute is only used with PCI d= evices - and is ignored by all the other device types, thus setting - managed explicitly with other than PCI device has t= he same - effect as omitting it. + Note: The managed attribute is only used with PCI a= nd + mediated devices and is ignored by all the other device types, t= hus + setting managed explicitly with other than a PCI or= a + mediated device has the same effect as omitting it.

source
@@ -3879,6 +3901,16 @@ is the vhost_scsi wwpn (16 hexadecimal digits with a prefix of "naa.") established in the host configfs. +
mdev
+
Mediated devices (Since 3.1.0) = are + described by the PCI address of the backing physical + parent device. Additionally, the mediated device is further iden= tified + by the uuid element. The element is optional if + managed=3D"yes", in which case the UUID shall be + generated automatically along with creation with the mediated + device. However, when managed=3D"no" then uui= d + element is mandatory. +
vendor, product
--=20 2.10.2 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list