debuggers.hg

view tools/python/xen/xend/tests/xend-config.sxp @ 0:7d21f7218375

Exact replica of unstable on 051908 + README-this
author Mukesh Rathor
date Mon May 19 15:34:57 2008 -0700 (2008-05-19)
parents
children
line source
1 # -*- sh -*-
3 #
4 # Xend configuration file.
5 #
7 # This example configuration is appropriate for an installation that
8 # utilizes a bridged network configuration. Access to xend via http
9 # is disabled.
11 # Commented out entries show the default for that entry, unless otherwise
12 # specified.
14 #(logfile /var/log/xend.log)
15 #(loglevel DEBUG)
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)
24 #(xend-unix-path /var/lib/xend/xend-socket)
26 # Port xend should use for the HTTP interface, if xend-http-server is set.
27 #(xend-port 8000)
29 # Port xend should use for the relocation interface, if xend-relocation-server
30 # is set.
31 #(xend-relocation-port 8002)
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)
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 '')
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$')
59 # The limit (in kilobytes) on the size of the console buffer
60 #(console-limit 1024)
62 ##
63 # To bridge network traffic, like this:
64 #
65 #
66 # dom0: ----------------- bridge -> real eth0 -> the network
67 # |
68 # domU: fake eth0 -> vifN.0 -+
69 #
70 # use
71 #
72 # (network-script network-bridge)
73 #
74 # Your default ethernet device is used as the outgoing interface, by default.
75 # To use a different one (e.g. eth1) use
76 #
77 # (network-script 'network-bridge netdev=eth1')
78 #
79 # The bridge is named xenbr0, by default. To rename the bridge, use
80 #
81 # (network-script 'network-bridge bridge=<name>')
82 #
83 # It is possible to use the network-bridge script in more complicated
84 # scenarios, such as having two outgoing interfaces, with two bridges, and
85 # two fake interfaces per guest domain. To do things like this, write
86 # yourself a wrapper script, and call network-bridge from it, as appropriate.
87 #
88 (network-script network-bridge)
90 # The script used to control virtual interfaces. This can be overridden on a
91 # per-vif basis when creating a domain or a configuring a new vif. The
92 # vif-bridge script is designed for use with the network-bridge script, or
93 # similar configurations.
94 #
95 # If you have overridden the bridge name using
96 # (network-script 'network-bridge bridge=<name>') then you may wish to do the
97 # same here. The bridge name can also be set when creating a domain or
98 # configuring a new vif, but a value specified here would act as a default.
99 #
100 # If you are using only one bridge, the vif-bridge script will discover that,
101 # so there is no need to specify it explicitly.
102 #
103 (vif-script vif-bridge)
106 ## Use the following if network traffic is routed, as an alternative to the
107 # settings for bridged networking given above.
108 #(network-script network-route)
109 #(vif-script vif-route)
112 ## Use the following if network traffic is routed with NAT, as an alternative
113 # to the settings for bridged networking given above.
114 #(network-script network-nat)
115 #(vif-script vif-nat)
118 # Dom0 will balloon out when needed to free memory for domU.
119 # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
120 # If dom0-min-mem=0, dom0 will never balloon out.
121 (dom0-min-mem 196)
123 # In SMP system, dom0 will use dom0-cpus # of CPUS
124 # If dom0-cpus = 0, dom0 will take all cpus available
125 (dom0-cpus 0)
127 # Whether to enable core-dumps when domains crash.
128 #(enable-dump no)
130 # The tool used for initiating virtual TPM migration
131 #(external-migration-tool '')