source: trunk/packages/xen-3.1/xen-3.1/tools/python/xen/xend/tests/xend-config.sxp @ 34

Last change on this file since 34 was 34, checked in by hartmans, 18 years ago

Add xen and xen-common

File size: 4.3 KB
Line 
1# -*- sh -*-
2
3#
4# Xend configuration file.
5#
6
7# This example configuration is appropriate for an installation that
8# utilizes a bridged network configuration. Access to xend via http
9# is disabled. 
10
11# Commented out entries show the default for that entry, unless otherwise
12# specified.
13
14#(logfile /var/log/xend.log)
15#(loglevel DEBUG)
16
17#(xend-http-server no)
18#(xend-unix-server no)
19#(xend-tcp-xmlrpc-server no)
20#(xend-unix-xmlrpc-server yes)
21#(xend-relocation-server no)
22(xend-relocation-server yes)
23
24#(xend-unix-path /var/lib/xend/xend-socket)
25
26# Port xend should use for the HTTP interface, if xend-http-server is set.
27#(xend-port            8000)
28
29# Port xend should use for the relocation interface, if xend-relocation-server
30# is set.
31#(xend-relocation-port 8002)
32
33# Address xend should listen on for HTTP connections, if xend-http-server is
34# set.
35# Specifying 'localhost' prevents remote connections.
36# Specifying the empty string '' (the default) allows all connections.
37#(xend-address '')
38#(xend-address localhost)
39
40# Address xend should listen on for relocation-socket connections, if
41# xend-relocation-server is set.
42# Meaning and default as for xend-address above.
43#(xend-relocation-address '')
44
45# The hosts allowed to talk to the relocation port.  If this is empty (the
46# default), then all connections are allowed (assuming that the connection
47# arrives on a port and interface on which we are listening; see
48# xend-relocation-port and xend-relocation-address above).  Otherwise, this
49# should be a space-separated sequence of regular expressions.  Any host with
50# a fully-qualified domain name or an IP address that matches one of these
51# regular expressions will be accepted.
52#
53# For example:
54#  (xend-relocation-hosts-allow '^localhost$ ^.*\\.example\\.org$')
55#
56#(xend-relocation-hosts-allow '')
57(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
58
59# The limit (in kilobytes) on the size of the console buffer
60#(console-limit 1024)
61
62##
63# To bridge network traffic, like this:
64#
65# dom0: fake eth0 -> vif0.0 -+
66#                            |
67#                          bridge -> real eth0 -> the network
68#                            |
69# domU: fake eth0 -> vifN.0 -+
70#
71# use
72#
73# (network-script network-bridge)
74#
75# Your default ethernet device is used as the outgoing interface, by default.
76# To use a different one (e.g. eth1) use
77#
78# (network-script 'network-bridge netdev=eth1')
79#
80# The bridge is named xenbr0, by default.  To rename the bridge, use
81#
82# (network-script 'network-bridge bridge=<name>')
83#
84# It is possible to use the network-bridge script in more complicated
85# scenarios, such as having two outgoing interfaces, with two bridges, and
86# two fake interfaces per guest domain.  To do things like this, write
87# yourself a wrapper script, and call network-bridge from it, as appropriate.
88#
89(network-script network-bridge)
90
91# The script used to control virtual interfaces.  This can be overridden on a
92# per-vif basis when creating a domain or a configuring a new vif.  The
93# vif-bridge script is designed for use with the network-bridge script, or
94# similar configurations.
95#
96# If you have overridden the bridge name using
97# (network-script 'network-bridge bridge=<name>') then you may wish to do the
98# same here.  The bridge name can also be set when creating a domain or
99# configuring a new vif, but a value specified here would act as a default.
100#
101# If you are using only one bridge, the vif-bridge script will discover that,
102# so there is no need to specify it explicitly.
103#
104(vif-script vif-bridge)
105
106
107## Use the following if network traffic is routed, as an alternative to the
108# settings for bridged networking given above.
109#(network-script network-route)
110#(vif-script     vif-route)
111
112
113## Use the following if network traffic is routed with NAT, as an alternative
114# to the settings for bridged networking given above.
115#(network-script network-nat)
116#(vif-script     vif-nat)
117
118
119# Dom0 will balloon out when needed to free memory for domU.
120# dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
121# If dom0-min-mem=0, dom0 will never balloon out.
122(dom0-min-mem 196)
123
124# In SMP system, dom0 will use dom0-cpus # of CPUS
125# If dom0-cpus = 0, dom0 will take all cpus available
126(dom0-cpus 0)
127
128# Whether to enable core-dumps when domains crash.
129#(enable-dump no)
130
131# The tool used for initiating virtual TPM migration
132#(external-migration-tool '')
Note: See TracBrowser for help on using the repository browser.