'boot' tag shouldn't be exclusive with 'kernel', 'initrd', and 'cmdline',
though the boot sequence doesn't make sense when the guest boots from
kernel directly. But it's useful if booting from kernel is to install
a newly guest, even it's not to install a guest, there is no hurt. And
on the other hand, we allow 'boot' and the kernel tags when parsing.
---
docs/schemas/domaincommon.rng | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/schemas/domaincommon.rng b/docs/schemas/domaincommon.rng
index 62c28c8..46e539d 100644
--- a/docs/schemas/domaincommon.rng
+++ b/docs/schemas/domaincommon.rng
@@ -222,12 +222,14 @@
<ref name="absFilePath"/>
</element>
</optional>
- <choice>
+ <optional>
<ref name="osbootkernel"/>
+ </optional>
+ <optional>
<zeroOrMore>
<ref name="osbootdev"/>
</zeroOrMore>
- </choice>
+ </optional>
<optional>
<element name="bootmenu">
<attribute name="enable">
--
1.7.7.3
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list