mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-25 01:34:11 +03:00
71 lines
2.9 KiB
HTML
71 lines
2.9 KiB
HTML
|
<html>
|
||
|
|
<body>
|
||
|
|
<h1>Driver capabilities XML format</h1>
|
||
|
|
|
||
|
|
<p>As new virtualization engine support gets added to libvirt, and to handle
|
||
|
|
cases like QEmu supporting a variety of emulations, a query interface has
|
||
|
|
been added in 0.2.1 allowing to list the set of supported virtualization
|
||
|
|
capabilities on the host:</p>
|
||
|
|
<pre> char * virConnectGetCapabilities (virConnectPtr conn);</pre>
|
||
|
|
<p>The value returned is an XML document listing the virtualization
|
||
|
|
capabilities of the host and virtualization engine to which
|
||
|
|
<code>@conn</code> is connected. One can test it using <code>virsh</code>
|
||
|
|
command line tool command '<code>capabilities</code>', it dumps the XML
|
||
|
|
associated to the current connection. For example in the case of a 64 bits
|
||
|
|
machine with hardware virtualization capabilities enabled in the chip and
|
||
|
|
BIOS you will see</p>
|
||
|
|
<pre><capabilities>
|
||
|
|
<span style="color: #E50000"><host>
|
||
|
|
<cpu>
|
||
|
|
<arch>x86_64</arch>
|
||
|
|
<features>
|
||
|
|
<vmx/>
|
||
|
|
</features>
|
||
|
|
</cpu>
|
||
|
|
</host></span>
|
||
|
|
|
||
|
|
<!-- xen-3.0-x86_64 -->
|
||
|
|
<span style="color: #0000E5"><guest>
|
||
|
|
<os_type>xen</os_type>
|
||
|
|
<arch name="x86_64">
|
||
|
|
<wordsize>64</wordsize>
|
||
|
|
<domain type="xen"></domain>
|
||
|
|
<emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
|
||
|
|
</arch>
|
||
|
|
<features>
|
||
|
|
</features>
|
||
|
|
</guest></span>
|
||
|
|
|
||
|
|
<!-- hvm-3.0-x86_32 -->
|
||
|
|
<span style="color: #00B200"><guest>
|
||
|
|
<os_type>hvm</os_type>
|
||
|
|
<arch name="i686">
|
||
|
|
<wordsize>32</wordsize>
|
||
|
|
<domain type="xen"></domain>
|
||
|
|
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
|
||
|
|
<machine>pc</machine>
|
||
|
|
<machine>isapc</machine>
|
||
|
|
<loader>/usr/lib/xen/boot/hvmloader</loader>
|
||
|
|
</arch>
|
||
|
|
<features>
|
||
|
|
</features>
|
||
|
|
</guest></span>
|
||
|
|
...
|
||
|
|
</capabilities></pre>
|
||
|
|
<p>The first block (in red) indicates the host hardware capabilities, currently
|
||
|
|
it is limited to the CPU properties but other information may be available,
|
||
|
|
it shows the CPU architecture, and the features of the chip (the feature
|
||
|
|
block is similar to what you will find in a Xen fully virtualized domain
|
||
|
|
description).</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 information and potential features.</p>
|
||
|
|
<p>The third block (in green) gives similar information but when running a
|
||
|
|
32 bit OS fully virtualized with Xen using the hvm support.</p>
|
||
|
|
<p>This section is likely to be updated and augmented in the future, see <a href="https://www.redhat.com/archives/libvir-list/2007-March/msg00215.html">the
|
||
|
|
discussion</a> which led to the capabilities format in the mailing-list
|
||
|
|
archives.</p>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|