Re: [libvirt] [PATCH 11/12] Expose IOMMU and VFIO capabilities from virCaps

This piece of information may be useful for management application to decide if a domain with a device passthrough can be started on given host or not. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com&gt; --- Notes: I'm not very happy with the element names, but they're the best I could come up with so far. If you have any better suggestion I am all ears. docs/formatcaps.html.in | 8 +++++++- docs/schemas/capability.rng | 12 ++++++++++++ src/conf/capabilities.c | 4 ++++ tests/capabilityschemadata/caps-qemu-kvm.xml | 2 ++ tests/capabilityschemadata/caps-test.xml | 2 ++ tests/capabilityschemadata/caps-test2.xml | 2 ++ tests/capabilityschemadata/caps-test3.xml | 2 ++ tests/xencapsdata/xen-i686-pae-hvm.xml | 2 ++ tests/xencapsdata/xen-i686-pae.xml | 2 ++ tests/xencapsdata/xen-i686.xml | 2 ++ tests/xencapsdata/xen-ia64-be-hvm.xml | 2 ++ tests/xencapsdata/xen-ia64-be.xml | 2 ++ tests/xencapsdata/xen-ia64-hvm.xml | 2 ++ tests/xencapsdata/xen-ia64.xml | 2 ++ tests/xencapsdata/xen-ppc64.xml | 2 ++ tests/xencapsdata/xen-x86_64-hvm.xml | 2 ++ tests/xencapsdata/xen-x86_64.xml | 2 ++ 17 files changed, 51 insertions(+), 1 deletion(-) diff --git a/docs/formatcaps.html.in b/docs/formatcaps.html.in index d060a5b..eb8c905 100644 --- a/docs/formatcaps.html.in +++ b/docs/formatcaps.html.in @@ -35,6 +35,8 @@ BIOS you will see</p> &lt;suspend_disk/&gt; &lt;suspend_hybrid/&gt; &lt;power_management/&gt; + &lt;kvm&gt;true&lt;/kvm&gt; + &lt;vfio&gt;true&lt;/vfio&gt; &lt;/host&gt;</span> &lt;!-- xen-3.0-x86_64 --&gt; @@ -78,7 +80,11 @@ BIOS you will see</p> Suspend-to-Disk (S4) and Hybrid-Suspend (a combination of S3 and S4). In case the host does not support any such feature, then an empty &lt;power_management/&gt; - tag will be shown. </p> + tag will be shown. Then, two elements + <code>&lt;kvm/&gt;</code> and <code>&lt;vfio/&gt;</code> + expose the fact, whether the host supports legacy device + passthrough with IOMMU cooperation or newer Virtual function + I/O.</p> <p>The second block (in blue) indicates the paravirtualization support of the Xen support, you will see the os_type of xen to indicate a paravirtual kernel, then architecture diff --git a/docs/schemas/capability.rng b/docs/schemas/capability.rng index d2d9776..3b378eb 100644 --- a/docs/schemas/capability.rng +++ b/docs/schemas/capability.rng @@ -48,6 +48,18 @@ <zeroOrMore> <ref name='secmodel'/> </zeroOrMore> + <element name='kvm'> + <choice> + <value>false</value> + <value>true</value> + </choice> + </element> + <element name='vfio'> + <choice> + <value>false</value> + <value>true</value> + </choice> + </element> </element> </define> diff --git a/src/conf/capabilities.c b/src/conf/capabilities.c index 9561ba3..a91f37b 100644 --- a/src/conf/capabilities.c +++ b/src/conf/capabilities.c @@ -901,6 +901,10 @@ virCapabilitiesFormatXML(virCapsPtr caps) virBufferAddLit(&buf, "</secmodel>\n"); } + /* KVM and VFIO features */ + virBufferAsprintf(&buf, "<kvm>%s</kvm>\n", caps->host.legacyKVMPassthrough ? "true" : "false"); + virBufferAsprintf(&buf, "<vfio>%s</vfio>\n", caps->host.VFIOPassthrough ? "true" : "false");