shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-11 09:17:52 +03:00
Code Releases Activity

docs: fix grammar of capabilities

Browse Source 
* docs/formatcaps.html.in: Avoid run-on sentence, wrap lines.
This commit is contained in:
Eric Blake 2011-11-22 10:30:07 -07:00
parent 720442e245
commit aa69441cba
1 changed files with 26 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
docs/formatcaps.html.in
View File

@ -64,25 +64,32 @@ BIOS you will see</p>
&lt;/guest&gt;</span>
...
&lt;/capabilities&gt;</pre>
<p>The first block (in red) indicates the host hardware capabilities, currently
it is limited to the CPU properties and the power management features of
the host platform, but other information may be available, it shows the CPU architecture,
topology, model name, and additional features which are not included in the model but the
CPU provides them. Features of the chip are shown within the feature block (the block is
similar to what you will find in a Xen fully virtualized domain description). Further,
the power management features supported by the host are shown, such as Suspend-to-RAM (S3)
and Suspend-to-Disk (S4). In case the query for power management features succeeded but the
host does not support any such feature, then an empty &lt;power_management/&gt;
tag will be shown. Otherwise, if the query itself failed, no such tag will
be displayed (i.e., there will not be any power_management block or empty tag in the XML).</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>
<p>The first block (in red) indicates the host hardware
capabilities, such as CPU properties and the power
management features of the host platform. CPU models are
shown as additional features relative to the closest base
model, within a feature block (the block is similar to what
you will find in a Xen fully virtualized domain
description). Further, the power management features
supported by the host are shown, such as Suspend-to-RAM (S3)
and Suspend-to-Disk (S4). In case the query for power
management features succeeded but the host does not support
any such feature, then an empty &lt;power_management/&gt;
tag will be shown. Otherwise, if the query itself failed, no
such tag will be displayed (i.e., there will not be any
power_management block or empty tag in the XML).</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>