Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openeuler
libvirt
提交
72e8284c
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,发现更多精彩内容 >>
提交
72e8284c
编写于
1月 10, 2007
作者:
D
Daniel Veillard
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
* docs/libvirt.rng: udated for the upcoming KVM and QEmu support
Daniel
上级
4dce3d8f
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
172 addition
and
8 deletion
+172
-8
ChangeLog
ChangeLog
+4
-0
docs/libvirt.rng
docs/libvirt.rng
+168
-8
未找到文件。
ChangeLog
浏览文件 @
72e8284c
Wed Jan 10 16:20:02 CET 2007 Daniel Veillard <veillard@redhat.com>
* docs/libvirt.rng: udated for the upcoming KVM and QEmu support
Wed Jan 10 11:06:36 CET 2007 Daniel Veillard <veillard@redhat.com>
Wed Jan 10 11:06:36 CET 2007 Daniel Veillard <veillard@redhat.com>
* docs/libvirt.rng: went through the existing tests with the RNG and
* docs/libvirt.rng: went through the existing tests with the RNG and
...
...
docs/libvirt.rng
浏览文件 @
72e8284c
...
@@ -8,13 +8,29 @@
...
@@ -8,13 +8,29 @@
<!--
<!--
We handle only document defining a domain
We handle only document defining a domain
Currently the only type supported is 'xen'
Currently the virtualization types supported are:
- xen, either paravirualized with a linux os or fully virtualized (hvm)
- kvm, requiring a path to the emulator in devices
- qemu, where the arch and machine must be provided in the os block
-->
<define
name=
'domain'
>
<element
name=
"domain"
>
<choice>
<ref
name=
'xen-domain'
/>
<ref
name=
'kvm-domain'
/>
<ref
name=
'qemu-domain'
/>
</choice>
</element>
</define>
<!--
Description of a Xen domain:
The description must start with the identification informations and then
The description must start with the identification informations and then
os or bootloader, resources, features, devices and termination informations
os or bootloader, resources, features, devices and termination informations
can be given in any order.
can be given in any order.
-->
-->
<define
name=
'domain'
>
<define
name=
'
xen-
domain'
>
<
element
name=
"domain"
>
<
group
>
<attribute
name=
'type'
>
<attribute
name=
'type'
>
<value>
xen
</value>
<value>
xen
</value>
</attribute>
</attribute>
...
@@ -39,7 +55,115 @@
...
@@ -39,7 +55,115 @@
<ref
name=
'termination'
/>
<ref
name=
'termination'
/>
<ref
name=
'devices'
/>
<ref
name=
'devices'
/>
</interleave>
</interleave>
</element>
</group>
</define>
<!--
Description of a QEmu domain:
The description must start with the identification informations and then
os, resources, devices can be given in any order.
The specific part are the combinations of architectures and machines
being emulated.
-->
<define
name=
'qemu-domain'
>
<group>
<attribute
name=
'type'
>
<value>
qemu
</value>
</attribute>
<ref
name=
'ids'
/>
<interleave>
<element
name=
'os'
>
<element
name=
'type'
>
<choice>
<ref
name=
'qemu-x86'
/>
<ref
name=
'qemu-mips'
/>
<ref
name=
'qemu-sparc'
/>
<ref
name=
'qemu-ppc'
/>
</choice>
<value>
hvm
</value>
</element>
</element>
<ref
name=
'resources'
/>
<ref
name=
'devices'
/>
</interleave>
</group>
</define>
<define
name=
'qemu-x86'
>
<group>
<attribute
name=
'arch'
>
<choice>
<value>
x86_64
</value>
<value>
x86_64
</value>
</choice>
</attribute>
<attribute
name=
'machine'
>
<choice>
<value>
pc
</value>
<value>
isapc
</value>
</choice>
</attribute>
</group>
</define>
<define
name=
'qemu-mips'
>
<group>
<attribute
name=
'arch'
>
<value>
mips
</value>
</attribute>
<attribute
name=
'machine'
>
<value>
mips
</value>
</attribute>
</group>
</define>
<define
name=
'qemu-sparc'
>
<group>
<attribute
name=
'arch'
>
<value>
sparc
</value>
</attribute>
<attribute
name=
'machine'
>
<value>
sun4m
</value>
</attribute>
</group>
</define>
<define
name=
'qemu-ppc'
>
<group>
<attribute
name=
'arch'
>
<value>
ppc
</value>
</attribute>
<attribute
name=
'machine'
>
<choice>
<value>
g3bw
</value>
<value>
mac99
</value>
<value>
prep
</value>
</choice>
</attribute>
</group>
</define>
<!--
Description of a KVM domain:
The description must start with the identification informations and then
os, resources, devices can be given in any order.
-->
<define
name=
'kvm-domain'
>
<group>
<attribute
name=
'type'
>
<value>
kvm
</value>
</attribute>
<ref
name=
'ids'
/>
<interleave>
<element
name=
'os'
>
<element
name=
'type'
>
<value>
hvm
</value>
</element>
</element>
<ref
name=
'resources'
/>
<ref
name=
'devices-with-emulator'
/>
</interleave>
</group>
</define>
</define>
<!--
<!--
...
@@ -301,6 +425,14 @@
...
@@ -301,6 +425,14 @@
<ref
name=
'interface-options'
/>
<ref
name=
'interface-options'
/>
</interleave>
</interleave>
</group>
</group>
<group>
<attribute
name=
'type'
>
<value>
user
</value>
</attribute>
<interleave>
<ref
name=
'interface-options'
/>
</interleave>
</group>
</choice>
</choice>
</element>
</element>
</define>
</define>
...
@@ -310,6 +442,7 @@
...
@@ -310,6 +442,7 @@
- the MAC address
- the MAC address
- the IP address bound to the interface
- the IP address bound to the interface
- the name of the script used to set up the binding
- the name of the script used to set up the binding
- the target device used
-->
-->
<define
name=
'interface-options'
>
<define
name=
'interface-options'
>
<interleave>
<interleave>
...
@@ -473,6 +606,29 @@
...
@@ -473,6 +606,29 @@
</element>
</element>
</define>
</define>
<!--
Sometimes the emulator is mandatory, e.g. with KVM
-->
<define
name=
'devices-with-emulator'
>
<element
name=
'devices'
>
<interleave>
<ref
name=
'emulator'
/>
<optional>
<ref
name=
'graphic'
/>
</optional>
<zeroOrMore>
<ref
name=
'disk'
/>
</zeroOrMore>
<zeroOrMore>
<ref
name=
'interface'
/>
</zeroOrMore>
<optional>
<ref
name=
'console'
/>
</optional>
</interleave>
</element>
</define>
<!--
<!--
A set of optional features: PAE, APIC and ACPI support
A set of optional features: PAE, APIC and ACPI support
-->
-->
...
@@ -541,10 +697,14 @@
...
@@ -541,10 +697,14 @@
</data>
</data>
</define>
</define>
<define
name=
'UUID'
>
<define
name=
'UUID'
>
<!-- TODO: be more flexible on UUID -->
<choice>
<data
type=
'string'
>
<data
type=
'string'
>
<param
name=
"pattern"
>
[a-fA-F0-9]{32}
</param>
<param
name=
"pattern"
>
[a-fA-F0-9]{32}
</param>
</data>
</data>
<data
type=
'string'
>
<param
name=
"pattern"
>
[a-fA-F0-9]{8}\-([a-fA-F0-9]{4}\-){3}[a-fA-F0-9]{12}
</param>
</data>
</choice>
</define>
</define>
<define
name=
'filePath'
>
<define
name=
'filePath'
>
<data
type=
'string'
>
<data
type=
'string'
>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录