The RNG structure is modified in order a user can instantiate a domain with a
new kind of device. By adding the device sub-tag <domaindependency>, the user
can link to another XML file, describing the domain to depend on.
For example, if a master domains specify in its XML description :
<devices>
..
<domaindependency> ~/slave_domain.xml </domaindependency>
...
</devices>
Then, the slave domain (described by the file slave_domain.xml) will be loaded
in the meantime.
The filepath must be absolute, because all the operations are done by the
libvirt daemon.
---
docs/schemas/domaincommon.rng | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/docs/schemas/domaincommon.rng b/docs/schemas/domaincommon.rng
index 8c6287d..77e7667 100644
--- a/docs/schemas/domaincommon.rng
+++ b/docs/schemas/domaincommon.rng
@@ -4097,6 +4097,7 @@
<ref name="tpm"/>
<ref name="shmem"/>
<ref name="memorydev"/>
+ <ref name="domaindependency"/>
</choice>
</zeroOrMore>
<optional>
@@ -4609,6 +4610,10 @@
</element>
</define>
+ <define name="domaindependency">
+ <element name="domaindependency"/>
+ </define>
+
<define name="rng">
<element name="rng">
<attribute name="model">
--
1.9.1