Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openeuler
libvirt
提交
f0088c1b
L
libvirt
项目概览
openeuler
/
libvirt
通知
3
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
L
libvirt
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
f0088c1b
编写于
1月 19, 2010
作者:
J
Jiri Denemark
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Document <cpu> elements in capabilities and domain XML
Signed-off-by:
N
Jiri Denemark
<
jdenemar@redhat.com
>
上级
d392f4db
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
103 addition
and
3 deletion
+103
-3
docs/formatcaps.html.in
docs/formatcaps.html.in
+10
-3
docs/formatdomain.html.in
docs/formatdomain.html.in
+93
-0
未找到文件。
docs/formatcaps.html.in
浏览文件 @
f0088c1b
...
@@ -21,6 +21,11 @@ BIOS you will see</p>
...
@@ -21,6 +21,11 @@ BIOS you will see</p>
<
features
>
<
features
>
<
vmx/
>
<
vmx/
>
<
/features
>
<
/features
>
<
model
>
core2duo
<
/model
>
<
topology sockets="1" cores="2" threads="1"/
>
<
feature name="lahf_lm"/
>
<
feature name='xtpr'/
>
...
<
/cpu
>
<
/cpu
>
<
/host
>
</span>
<
/host
>
</span>
...
@@ -48,15 +53,17 @@ BIOS you will see</p>
...
@@ -48,15 +53,17 @@ BIOS you will see</p>
<
loader
>
/usr/lib/xen/boot/hvmloader
<
/loader
>
<
loader
>
/usr/lib/xen/boot/hvmloader
<
/loader
>
<
/arch
>
<
/arch
>
<
features
>
<
features
>
<
cpuselection/
>
<
/features
>
<
/features
>
<
/guest
>
</span>
<
/guest
>
</span>
...
...
<
/capabilities
>
</pre>
<
/capabilities
>
</pre>
<p>
The first block (in red) indicates the host hardware capabilities, currently
<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 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
it shows the CPU architecture, topology, model name, and additional features
block is similar to what you will find in a Xen fully virtualized domain
which are not included in the model but the CPU provides them. Features of the
description).
</p>
chip are shown within the feature block (the 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
<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
Xen support, you will see the os_type of xen to indicate a paravirtual
kernel, then architecture information and potential features.
</p>
kernel, then architecture information and potential features.
</p>
...
...
docs/formatdomain.html.in
浏览文件 @
f0088c1b
...
@@ -201,6 +201,99 @@
...
@@ -201,6 +201,99 @@
CPUs allocated for the guest OS.
</dd>
CPUs allocated for the guest OS.
</dd>
</dl>
</dl>
<h3><a
name=
"elementsCPU"
>
CPU model and topology
</a></h3>
<p>
Requirements for CPU model, its features and topology can be specified
using the following collection of elements.
<span
class=
"since"
>
Since 0.7.5
</span>
</p>
<pre>
...
<
cpu match='exact'
>
<
model
>
core2duo
<
/model
>
<
topology sockets='1' cores='2' threads='1'/
>
<
feature policy='disable' name='lahf_lm'/
>
<
/cpu
>
...
</pre>
<p>
In case no restrictions need to be put on CPU model and its features, a
simpler
<code>
cpu
</code>
element can be used.
<span
class=
"since"
>
Since 0.7.6
</span>
</p>
<pre>
...
<
cpu
>
<
topology sockets='1' cores='2' threads='1'/
>
<
/cpu
>
...
</pre>
<dl>
<dt><code>
cpu
</code></dt>
<dd>
The
<code>
cpu
</code>
element is the main container for describing
guest CPU requirements. Its
<code>
match
</code>
attribute specified how
strictly has the virtual CPU provided to the guest match these
requirements.
<span
class=
"since"
>
Since 0.7.6
</span>
the
<code>
match
</code>
attribute can be omitted if
<code>
topology
</code>
is the only element within
<code>
cpu
</code>
. Possible values for the
<code>
match
</code>
attribute are:
<dl>
<dt><code>
minimum
</code></dt>
<dd>
The specified CPU model and features describes the minimum
requested CPU.
</dd>
<dt><code>
exact
</code></dt>
<dd>
The virtual CPU provided to the guest will exactly match the
specification
</dd>
<dt><code>
strict
</code></dt>
<dd>
The guest will not be created unless the host CPU does exactly
match the specification.
</dd>
</dl>
</dd>
<dt><code>
model
</code></dt>
<dd>
The content of the
<code>
model
</code>
element specifies CPU model
requested by the guest. The list of available CPU models and their
definition can be found in
<code>
cpu_map.xml
</code>
file installed
in libvirt's data directory.
</dd>
<dt><code>
topology
</code></dt>
<dd>
The
<code>
topology
</code>
element specifies requested topology of
virtual CPU provided to the guest. Three non-zero values have to be
given for
<code>
sockets
</code>
,
<code>
cores
</code>
, and
<code>
threads
</code>
: total number of CPU sockets, number of cores per
socket, and number of threads per core, respectively.
</dd>
<dt><code>
feature
</code></dt>
<dd>
The
<code>
cpu
</code>
element can contain zero or more
<code>
elements
</code>
used to fine-tune features provided by the
selected CPU model. The list of known feature names can be found in
the same file as CPU models. The meaning of each
<code>
feature
</code>
element depends on its
<code>
policy
</code>
attribute, which has to be
set to one of the following values:
<dl>
<dt><code>
force
</code></dt>
<dd>
The virtual CPU will claim the feature is supported regardless
of it being supported by host CPU.
</dd>
<dt><code>
require
</code></dt>
<dd>
Guest creation will fail unless the feature is supported by host
CPU.
</dd>
<dt><code>
optional
</code></dt>
<dd>
The feature will be supported by virtual CPU if and only if it
is supported by host CPU.
</dd>
<dt><code>
disable
</code></dt>
<dd>
The feature will not be supported by virtual CPU.
</dd>
<dt><code>
forbid
</code></dt>
<dd>
Guest creation will fail if the feature is supported by host
CPU.
</dd>
</dl>
</dd>
</dl>
<h3><a
name=
"elementsLifecycle"
>
Lifecycle control
</a></h3>
<h3><a
name=
"elementsLifecycle"
>
Lifecycle control
</a></h3>
<p>
<p>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录