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