xend-config.sxp - Xen daemon configuration file
/etc/xen/xend-config.sxp I think that you have to make this file (script) executable. As root,
chmod +x /etc/xen/xend-config.sxp
The xend(1) program requires xend-config.sxp to specify operating parameters which determine the behavior of the daemon at runtime.
The parameters are specified in S-expression format. See the example configuration file in /etc/xen/xend-config.sxp for details.
The example configuration is appropriate for an installation that utilizes a bridged network configuration. Access to xend via http is disabled.
The following lists the daemon configuration parameters:
The location of the file to record runtime log messages. Defaults to /var/log/xend.log
Filters out messages below the specified level. Possible values are DEBUG, INFO, WARNING, ERROR, CRITICAL. Defaults to DEBUG.
A boolean value that tells xend whether or not to start the http stream socket management server. Defaults to I<no>. wtf is this? we certainly don't need it to start the deamon or start and manage domUs. What extactly is this for?
A boolean value that tells xend whether or not to start the unix domain socket management server. This is required for the CLI tools to operate. Defaults to yes
OK. so it looks as if we **need** this even though it's set to no in the example file shown in /etc/xen.
A boolean value that tells xend whether or not to start the relocation server. This is required for cross-machine migrations. Defaults to no.
We will change this to no in the example file given.
The location of the unix domain socket the xend-unix-server will use to communicate with the management tools. Defaults to /var/lib/xend/xend-socket
The port that will be used by the http management server. Defaults to 8000
The port that will be used by the relocation server. Defaults to 8002.
The address to which the http management server will bind. Defaults to which means "all interfaces".
The address to which the relocation server will bind. Defaults to which means "all interfaces".
The kilobyte buffer limit that will be enforced by the console server. This limit is set per-domain, and is needed to prevent a single domain from overwhelming the console server with massive amounts of data. Defaults to 1024.
The name of the script in /etc/xen/scripts that will be run to setup the networking environment. This can be any name, but in setup the networking environment. This can be any name, but in general is either network-bridge or network-route.
The name of the script in /etc/xen/scripts that will be run to setup a virtual interface when it is created or destroyed. This needs to (in general) work in unison with the network-script.
This specifies the minimum number of megabytes that will be reserved for Domain0. If this value is positive, Domain0 will be automatically ballooned down to this limit to make space for new domains. If this is set to 0, Domain0 will not be automatically ballooned.
This specifies the number of CPUs that Domain0 will be allowed to use. If the value is 0, all available CPUs will be used by Domain0.
A boolean value that tells xend whether or not core dumps of guest domains should be saved when a crash occurrs. Defaults to I<no>.
An example configuration with relocation enabled for the local network:
(xend-relocation-server yes) (xend-relocation-address 192.168.1.1) (network-script network-bridge) (vif-script vif-bridge) (dom0-min-mem 0) (dom0-cpus 0)
Note that relocation is currently unsecured and is very dangerous if left enabled. No authentication is performed, and very little sanity checking takes place. Enable at your own risk.
The original author of these docs is Dan Smith <email@example.com>. I've just played about with xen a bit and added a few comments. jayeola - john maclean