source: trunk/packages/xen-3.1/xen-3.1/tools/examples/xend-config-xenapi.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: 6.8 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/xen/xend.log)
15#(loglevel DEBUG)
16
17
18# The Xen-API server configuration.  (Please note that this server is
19# available as an UNSUPPORTED PREVIEW in Xen 3.0.4, and should not be relied
20# upon).
21#
22# This value configures the ports, interfaces, and access controls for the
23# Xen-API server.  Each entry in the list starts with either unix, a port
24# number, or an address:port pair.  If this is "unix", then a UDP socket is
25# opened, and this entry applies to that.  If it is a port, then Xend will
26# listen on all interfaces on that TCP port, and if it is an address:port
27# pair, then Xend will listen on the specified port, using the interface with
28# the specified address.
29#
30# The subsequent string configures the user-based access control for the
31# listener in question.  This can be one of "none" or "pam", indicating either
32# that users should be allowed access unconditionally, or that the local
33# Pluggable Authentication Modules configuration should be used.  If this
34# string is missing or empty, then "pam" is used.
35#
36# The final string gives the host-based access control for that listener. If
37# this is missing or empty, then all connections are accepted.  Otherwise,
38# this should be a space-separated sequence of regular expressions; any host
39# with a fully-qualified domain name or an IP address that matches one of
40# these regular expressions will be accepted.
41#
42# Example: listen on TCP port 9363 on all interfaces, accepting connections
43# only from machines in example.com or localhost, and allow access through
44# the unix domain socket unconditionally:
45#
46   (xen-api-server ((9363 none)))
47#                    (unix none)))
48#
49# Optionally, the TCP Xen-API server can use SSL by specifying the private
50# key and certificate location:
51#
52#                    (9367 pam '' /etc/xen/xen-api.key /etc/xen/xen-api.crt)
53#
54# Default:
55#   (xen-api-server ((unix)))
56
57
58#(xend-http-server no)
59#(xend-unix-server no)
60#(xend-tcp-xmlrpc-server no)
61#(xend-unix-xmlrpc-server yes)
62#(xend-relocation-server no)
63(xend-relocation-server yes)
64
65#(xend-unix-path /var/lib/xend/xend-socket)
66
67
68# Address and port xend should use for the legacy TCP XMLRPC interface,
69# if xen-tcp-xmlrpc-server is set.
70#(xen-tcp-xmlrpc-server-address 'localhost')
71#(xen-tcp-xmlrpc-server-port 8006)
72
73# SSL key and certificate to use for the legacy TCP XMLRPC interface.
74# Setting these will mean that this port serves only SSL connections as
75# opposed to plaintext ones.
76#(xend-tcp-xmlrpc-server-ssl-key-file  /etc/xen/xmlrpc.key)
77#(xend-tcp-xmlrpc-server-ssl-cert-file /etc/xen/xmlrpc.crt)
78
79
80# Port xend should use for the HTTP interface, if xend-http-server is set.
81#(xend-port            8000)
82
83# Port xend should use for the relocation interface, if xend-relocation-server
84# is set.
85#(xend-relocation-port 8002)
86
87# Address xend should listen on for HTTP connections, if xend-http-server is
88# set.
89# Specifying 'localhost' prevents remote connections.
90# Specifying the empty string '' (the default) allows all connections.
91#(xend-address '')
92#(xend-address localhost)
93
94# Address xend should listen on for relocation-socket connections, if
95# xend-relocation-server is set.
96# Meaning and default as for xend-address above.
97#(xend-relocation-address '')
98
99# The hosts allowed to talk to the relocation port.  If this is empty (the
100# default), then all connections are allowed (assuming that the connection
101# arrives on a port and interface on which we are listening; see
102# xend-relocation-port and xend-relocation-address above).  Otherwise, this
103# should be a space-separated sequence of regular expressions.  Any host with
104# a fully-qualified domain name or an IP address that matches one of these
105# regular expressions will be accepted.
106#
107# For example:
108#  (xend-relocation-hosts-allow '^localhost$ ^.*\\.example\\.org$')
109#
110#(xend-relocation-hosts-allow '')
111(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
112
113# The limit (in kilobytes) on the size of the console buffer
114#(console-limit 1024)
115
116##
117# To bridge network traffic, like this:
118#
119# dom0: fake eth0 -> vif0.0 -+
120#                            |
121#                          bridge -> real eth0 -> the network
122#                            |
123# domU: fake eth0 -> vifN.0 -+
124#
125# use
126#
127# (network-script network-bridge)
128#
129# Your default ethernet device is used as the outgoing interface, by default.
130# To use a different one (e.g. eth1) use
131#
132# (network-script 'network-bridge netdev=eth1')
133#
134# The bridge is named xenbr0, by default.  To rename the bridge, use
135#
136# (network-script 'network-bridge bridge=<name>')
137#
138# It is possible to use the network-bridge script in more complicated
139# scenarios, such as having two outgoing interfaces, with two bridges, and
140# two fake interfaces per guest domain.  To do things like this, write
141# yourself a wrapper script, and call network-bridge from it, as appropriate.
142#
143(network-script network-bridge)
144
145# The script used to control virtual interfaces.  This can be overridden on a
146# per-vif basis when creating a domain or a configuring a new vif.  The
147# vif-bridge script is designed for use with the network-bridge script, or
148# similar configurations.
149#
150# If you have overridden the bridge name using
151# (network-script 'network-bridge bridge=<name>') then you may wish to do the
152# same here.  The bridge name can also be set when creating a domain or
153# configuring a new vif, but a value specified here would act as a default.
154#
155# If you are using only one bridge, the vif-bridge script will discover that,
156# so there is no need to specify it explicitly.
157#
158(vif-script vif-bridge)
159
160
161## Use the following if network traffic is routed, as an alternative to the
162# settings for bridged networking given above.
163#(network-script network-route)
164#(vif-script     vif-route)
165
166
167## Use the following if network traffic is routed with NAT, as an alternative
168# to the settings for bridged networking given above.
169#(network-script network-nat)
170#(vif-script     vif-nat)
171
172
173# Dom0 will balloon out when needed to free memory for domU.
174# dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
175# If dom0-min-mem=0, dom0 will never balloon out.
176(dom0-min-mem 196)
177
178# In SMP system, dom0 will use dom0-cpus # of CPUS
179# If dom0-cpus = 0, dom0 will take all cpus available
180(dom0-cpus 0)
181
182# Whether to enable core-dumps when domains crash.
183#(enable-dump no)
184
185# The tool used for initiating virtual TPM migration
186#(external-migration-tool '')
187
188# The interface for VNC servers to listen on. Defaults
189# to 127.0.0.1  To restore old 'listen everywhere' behaviour
190# set this to 0.0.0.0
191#(vnc-listen '127.0.0.1')
192
193# The default password for VNC console on HVM domain.
194# Empty string is no authentication.
195(vncpasswd '')
Note: See TracBrowser for help on using the repository browser.