Add xl domUs default configuration file
PATCH 1/1 Add xl domUs default configuration file
This patch add xl domUs default configuration file, must be improved and implemented in the core xl.
About implementation on core i try but fail, about this configuration file i start from other xm, removed some unnecessary things or specific such as name and uuid missed in xl and add other, some description need to be improved.
# HG changeset patch
# User Fabio Fantoni
# Date 1307358064 -7200
# Node ID b94e5d172a99a89e2bf1570ded6e41051ef81052
# Parent 0c0884fd8b494932a4b707e339cbe1b881d09103
Add xl domUs default configuration file, must be improved and implemented in the core xl
tools/examples/Makefile Mon Jun 06 13:01:04 2011 +0200 renamed from tools/examples/Makefile Fri Jun 03 21:39:00 2011 +0100 +1 -0
@@ -22,6 +22,7 @@ XEN_CONFIGS += xend-pci-quirks.sxp XEN_CONFIGS += xend-pci-permissive.sxp XEN_CONFIGS += xl.conf +XEN_CONFIGS += xl-domu-default.conf XEN_CONFIGS += cpupool .PHONY: all
tools/examples/xl-domu-default.conf Mon Jun 06 13:01:04 2011 +0200 renamed from dev/null Thu Jan 01 00:00:00 1970 +0000 +243 -0
243 lines not on this page · raw message
Fabio Fantoni writes ("[Xen-devel] [PATCH] Add xl domUs default configuration file"):
Quoted 2 lines
This patch add xl domUs default configuration file, must be improved and implemented in the core xl.
Thanks. But this file still contains a lot of things that ought never to be specified in a global file.
Also, I don't think it's appropriate for this file to essentially be a clone-and-hack of the example domain config file. I think an almost-empty placeholder would do fine.
Finally, having an example file of this kind is less important than having the code to actually parse it. We can't have an example file which if you uncomment things has no effect, so we can't have this file until the corresponding code is there.
Ian.