提交 aa69441c 编写于 作者: E Eric Blake

docs: fix grammar of capabilities

* docs/formatcaps.html.in: Avoid run-on sentence, wrap lines.
上级 720442e2
...@@ -64,25 +64,32 @@ BIOS you will see</p> ...@@ -64,25 +64,32 @@ BIOS you will see</p>
&lt;/guest&gt;</span> &lt;/guest&gt;</span>
... ...
&lt;/capabilities&gt;</pre> &lt;/capabilities&gt;</pre>
<p>The first block (in red) indicates the host hardware capabilities, currently <p>The first block (in red) indicates the host hardware
it is limited to the CPU properties and the power management features of capabilities, such as CPU properties and the power
the host platform, but other information may be available, it shows the CPU architecture, management features of the host platform. CPU models are
topology, model name, and additional features which are not included in the model but the shown as additional features relative to the closest base
CPU provides them. Features of the chip are shown within the feature block (the block is model, within a feature block (the block is similar to what
similar to what you will find in a Xen fully virtualized domain description). Further, you will find in a Xen fully virtualized domain
the power management features supported by the host are shown, such as Suspend-to-RAM (S3) description). Further, the power management features
and Suspend-to-Disk (S4). In case the query for power management features succeeded but the supported by the host are shown, such as Suspend-to-RAM (S3)
host does not support any such feature, then an empty &lt;power_management/&gt; and Suspend-to-Disk (S4). In case the query for power
tag will be shown. Otherwise, if the query itself failed, no such tag will management features succeeded but the host does not support
be displayed (i.e., there will not be any power_management block or empty tag in the XML).</p> any such feature, then an empty &lt;power_management/&gt;
<p>The second block (in blue) indicates the paravirtualization support of the tag will be shown. Otherwise, if the query itself failed, no
Xen support, you will see the os_type of xen to indicate a paravirtual such tag will be displayed (i.e., there will not be any
kernel, then architecture information and potential features.</p> power_management block or empty tag in the XML).</p>
<p>The third block (in green) gives similar information but when running a <p>The second block (in blue) indicates the paravirtualization
32 bit OS fully virtualized with Xen using the hvm support.</p> support of the Xen support, you will see the os_type of xen
<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 to indicate a paravirtual kernel, then architecture
discussion</a> which led to the capabilities format in the mailing-list information and potential features.</p>
archives.</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> </body>
</html> </html>
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册