Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openeuler
libvirt
提交
f5ade634
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,发现更多精彩内容 >>
提交
f5ade634
编写于
3月 07, 2008
作者:
D
Daniel Veillard
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
* docs/libvir.html docs/storage.html: apply documentation fixes
and typos cleanup from Atsushi Sakai Daniel
上级
d4cbf4c6
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
27 addition
and
22 deletion
+27
-22
ChangeLog
ChangeLog
+5
-0
docs/libvir.html
docs/libvir.html
+11
-11
docs/storage.html
docs/storage.html
+11
-11
未找到文件。
ChangeLog
浏览文件 @
f5ade634
Fri Mar 7 12:11:53 CET 2008 Daniel Veillard <veillard@redhat.com>
* docs/libvir.html docs/storage.html: apply documentation fixes
and typos cleanup from Atsushi Sakai
Fri Mar 7 10:22:00 CET 2008 Daniel Veillard <veillard@redhat.com>
Fri Mar 7 10:22:00 CET 2008 Daniel Veillard <veillard@redhat.com>
* src/xend_internal.c: applied patch from Cole Robinson to not
* src/xend_internal.c: applied patch from Cole Robinson to not
...
...
docs/libvir.html
浏览文件 @
f5ade634
...
@@ -4069,7 +4069,7 @@ full capacity for storage volumes. This value is in bytes. This
...
@@ -4069,7 +4069,7 @@ full capacity for storage volumes. This value is in bytes. This
is not applicable when creating a pool.
</dd>
is not applicable when creating a pool.
</dd>
<dt>
available
</dt>
<dt>
available
</dt>
<dd>
Providing the free space available for allocating new volums
<dd>
Providing the free space available for allocating new volum
e
s
in the pool. Due to underlying device constraints it may not be
in the pool. Due to underlying device constraints it may not be
possible to allocate the entire free space to a single volume.
possible to allocate the entire free space to a single volume.
This value is in bytes. This is not applicable when creating a
This value is in bytes. This is not applicable when creating a
...
@@ -4119,11 +4119,11 @@ value for this, so it is optional.</dd>
...
@@ -4119,11 +4119,11 @@ value for this, so it is optional.</dd>
<dd>
Provides the location at which the pool will be mapped into
<dd>
Provides the location at which the pool will be mapped into
the local filesystem namespace. For a filesystem/directory based
the local filesystem namespace. For a filesystem/directory based
pool it will be the name of the directory in which volumes will
pool it will be the name of the directory in which volumes will
be created. For device based pools it will
tb
e directory in which
be created. For device based pools it will
be the name of th
e directory in which
devices nodes exist. For the latter
<code>
/dev/
</code>
may seem
devices nodes exist. For the latter
<code>
/dev/
</code>
may seem
like the logical choice, however, devices nodes there are not
like the logical choice, however, devices nodes there are not
guar
e
nteed stable across reboots, since they are allocated on
guar
a
nteed stable across reboots, since they are allocated on
demand. It is prefer
r
able to use a stable location such as one
demand. It is preferable to use a stable location such as one
of the
<code>
/dev/disk/by-{path,id,uuid,label
</code>
locations.
of the
<code>
/dev/disk/by-{path,id,uuid,label
</code>
locations.
</dd>
</dd>
<dt>
permissions
<dt>
<dt>
permissions
<dt>
...
@@ -4145,7 +4145,7 @@ contains the MAC (eg SELinux) label string.
...
@@ -4145,7 +4145,7 @@ contains the MAC (eg SELinux) label string.
If a storage pool exposes information about its underlying
If a storage pool exposes information about its underlying
placement / allocation scheme, the
<code>
device
</code>
element
placement / allocation scheme, the
<code>
device
</code>
element
within the
<code>
source
</code>
element may contain information
within the
<code>
source
</code>
element may contain information
about its avilable extents. Some pools have a constraint that
about its av
a
ilable extents. Some pools have a constraint that
a volume must be allocated entirely within a single constraint
a volume must be allocated entirely within a single constraint
(eg disk partition pools). Thus the extent information allows an
(eg disk partition pools). Thus the extent information allows an
application to determine the maximum possible size for a new
application to determine the maximum possible size for a new
...
@@ -4209,10 +4209,10 @@ on the local host.</dd>
...
@@ -4209,10 +4209,10 @@ on the local host.</dd>
<dd>
Provides the location at which the pool will be mapped into
<dd>
Provides the location at which the pool will be mapped into
the local filesystem namespace. For a filesystem/directory based
the local filesystem namespace. For a filesystem/directory based
pool it will be the name of the directory in which volumes will
pool it will be the name of the directory in which volumes will
be created. For device based pools it will
tb
e directory in which
be created. For device based pools it will
be the name of th
e directory in which
devices nodes exist. For the latter
<code>
/dev/
</code>
may seem
devices nodes exist. For the latter
<code>
/dev/
</code>
may seem
like the logical choice, however, devices nodes there are not
like the logical choice, however, devices nodes there are not
guar
e
nteed stable across reboots, since they are allocated on
guar
a
nteed stable across reboots, since they are allocated on
demand. It is preferrable to use a stable location such as one
demand. It is preferrable to use a stable location such as one
of the
<code>
/dev/disk/by-{path,id,uuid,label
</code>
locations.
of the
<code>
/dev/disk/by-{path,id,uuid,label
</code>
locations.
</dd>
</dd>
...
@@ -4297,10 +4297,10 @@ One of the following options:
...
@@ -4297,10 +4297,10 @@ One of the following options:
<p>
<p>
When listing existing volumes all these formats are supported
When listing existing volumes all these formats are supported
natively. When creating new volumes, only a subset may be
natively. When creating new volumes, only a subset may be
available. The
<code>
raw
</code>
type is guar
e
nteed always
available. The
<code>
raw
</code>
type is guar
a
nteed always
available. The
<code>
qcow2
</code>
type can be created if
available. The
<code>
qcow2
</code>
type can be created if
either
<code>
qemu-img
</code>
or
<code>
qcow-create
</code>
tools
either
<code>
qemu-img
</code>
or
<code>
qcow-create
</code>
tools
are present. The others are depend
a
nt on support of the
are present. The others are depend
e
nt on support of the
<code>
qemu-img
</code>
tool.
<code>
qemu-img
</code>
tool.
<h4><a
name=
"StorageBackendFS"
>
Filesystem pool
</a></h4>
<h4><a
name=
"StorageBackendFS"
>
Filesystem pool
</a></h4>
...
@@ -4332,7 +4332,7 @@ required.
...
@@ -4332,7 +4332,7 @@ required.
<h5>
Valid pool format types
</h5>
<h5>
Valid pool format types
</h5>
<p>
<p>
The fileystem pool supports the following formats:
The file
s
ystem pool supports the following formats:
</p>
</p>
<ul>
<ul>
...
@@ -4385,7 +4385,7 @@ point. It will default to using NFS as the protocol.
...
@@ -4385,7 +4385,7 @@ point. It will default to using NFS as the protocol.
<h5>
Valid pool format types
</h5>
<h5>
Valid pool format types
</h5>
<p>
<p>
The network fileystem pool supports the following formats:
The network file
s
ystem pool supports the following formats:
</p>
</p>
<ul>
<ul>
...
...
docs/storage.html
浏览文件 @
f5ade634
...
@@ -84,7 +84,7 @@ full capacity for storage volumes. This value is in bytes. This
...
@@ -84,7 +84,7 @@ full capacity for storage volumes. This value is in bytes. This
is not applicable when creating a pool.
</dd>
is not applicable when creating a pool.
</dd>
<dt>
available
</dt>
<dt>
available
</dt>
<dd>
Providing the free space available for allocating new volums
<dd>
Providing the free space available for allocating new volum
e
s
in the pool. Due to underlying device constraints it may not be
in the pool. Due to underlying device constraints it may not be
possible to allocate the entire free space to a single volume.
possible to allocate the entire free space to a single volume.
This value is in bytes. This is not applicable when creating a
This value is in bytes. This is not applicable when creating a
...
@@ -128,11 +128,11 @@ value for this, so it is optional.</dd>
...
@@ -128,11 +128,11 @@ value for this, so it is optional.</dd>
<dd>
Provides the location at which the pool will be mapped into
<dd>
Provides the location at which the pool will be mapped into
the local filesystem namespace. For a filesystem/directory based
the local filesystem namespace. For a filesystem/directory based
pool it will be the name of the directory in which volumes will
pool it will be the name of the directory in which volumes will
be created. For device based pools it will
tb
e directory in which
be created. For device based pools it will
be the name of th
e directory in which
devices nodes exist. For the latter
<code>
/dev/
</code>
may seem
devices nodes exist. For the latter
<code>
/dev/
</code>
may seem
like the logical choice, however, devices nodes there are not
like the logical choice, however, devices nodes there are not
guar
e
nteed stable across reboots, since they are allocated on
guar
a
nteed stable across reboots, since they are allocated on
demand. It is prefer
r
able to use a stable location such as one
demand. It is preferable to use a stable location such as one
of the
<code>
/dev/disk/by-{path,id,uuid,label
</code>
locations.
of the
<code>
/dev/disk/by-{path,id,uuid,label
</code>
locations.
</dd>
</dd>
<dt>
permissions
<dt>
<dt>
permissions
<dt>
...
@@ -152,7 +152,7 @@ contains the MAC (eg SELinux) label string.
...
@@ -152,7 +152,7 @@ contains the MAC (eg SELinux) label string.
If a storage pool exposes information about its underlying
If a storage pool exposes information about its underlying
placement / allocation scheme, the
<code>
device
</code>
element
placement / allocation scheme, the
<code>
device
</code>
element
within the
<code>
source
</code>
element may contain information
within the
<code>
source
</code>
element may contain information
about its avilable extents. Some pools have a constraint that
about its av
a
ilable extents. Some pools have a constraint that
a volume must be allocated entirely within a single constraint
a volume must be allocated entirely within a single constraint
(eg disk partition pools). Thus the extent information allows an
(eg disk partition pools). Thus the extent information allows an
application to determine the maximum possible size for a new
application to determine the maximum possible size for a new
...
@@ -212,10 +212,10 @@ on the local host.</dd>
...
@@ -212,10 +212,10 @@ on the local host.</dd>
<dd>
Provides the location at which the pool will be mapped into
<dd>
Provides the location at which the pool will be mapped into
the local filesystem namespace. For a filesystem/directory based
the local filesystem namespace. For a filesystem/directory based
pool it will be the name of the directory in which volumes will
pool it will be the name of the directory in which volumes will
be created. For device based pools it will
tb
e directory in which
be created. For device based pools it will
be the name of th
e directory in which
devices nodes exist. For the latter
<code>
/dev/
</code>
may seem
devices nodes exist. For the latter
<code>
/dev/
</code>
may seem
like the logical choice, however, devices nodes there are not
like the logical choice, however, devices nodes there are not
guar
e
nteed stable across reboots, since they are allocated on
guar
a
nteed stable across reboots, since they are allocated on
demand. It is preferrable to use a stable location such as one
demand. It is preferrable to use a stable location such as one
of the
<code>
/dev/disk/by-{path,id,uuid,label
</code>
locations.
of the
<code>
/dev/disk/by-{path,id,uuid,label
</code>
locations.
</dd>
</dd>
...
@@ -293,10 +293,10 @@ One of the following options:
...
@@ -293,10 +293,10 @@ One of the following options:
</ul><p>
</ul><p>
When listing existing volumes all these formats are supported
When listing existing volumes all these formats are supported
natively. When creating new volumes, only a subset may be
natively. When creating new volumes, only a subset may be
available. The
<code>
raw
</code>
type is guar
e
nteed always
available. The
<code>
raw
</code>
type is guar
a
nteed always
available. The
<code>
qcow2
</code>
type can be created if
available. The
<code>
qcow2
</code>
type can be created if
either
<code>
qemu-img
</code>
or
<code>
qcow-create
</code>
tools
either
<code>
qemu-img
</code>
or
<code>
qcow-create
</code>
tools
are present. The others are depend
a
nt on support of the
are present. The others are depend
e
nt on support of the
<code>
qemu-img
</code>
tool.
<code>
qemu-img
</code>
tool.
</p><h4><a
name=
"StorageBackendFS"
id=
"StorageBackendFS"
>
Filesystem pool
</a></h4>
</p><h4><a
name=
"StorageBackendFS"
id=
"StorageBackendFS"
>
Filesystem pool
</a></h4>
...
@@ -328,7 +328,7 @@ required.
...
@@ -328,7 +328,7 @@ required.
<h5>
Valid pool format types
</h5>
<h5>
Valid pool format types
</h5>
<p>
<p>
The fileystem pool supports the following formats:
The file
s
ystem pool supports the following formats:
</p>
</p>
<ul><li><code>
auto
</code>
- automatically determine format
</li>
<ul><li><code>
auto
</code>
- automatically determine format
</li>
...
@@ -378,7 +378,7 @@ point. It will default to using NFS as the protocol.
...
@@ -378,7 +378,7 @@ point. It will default to using NFS as the protocol.
<h5>
Valid pool format types
</h5>
<h5>
Valid pool format types
</h5>
<p>
<p>
The network fileystem pool supports the following formats:
The network file
s
ystem pool supports the following formats:
</p>
</p>
<ul><li><code>
auto
</code>
- automatically determine format
</li>
<ul><li><code>
auto
</code>
- automatically determine format
</li>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录