Keep in mind that you need to reboot the host for the Xen server to make
the host accept your changes. We changed the following settings:
xend-relocation-server : This is a flag for enabling/disabling the relocation
server. By default, this is set to no to keep the relocation server deactivated.
During the process of migration, the domain virtual memory is exchanged in
raw format without any encryption. Make a note of this before enabling this
in an untrusted network.
xend-relocation-port : The port used by the xend daemon for relocation. The
default value for this port is 8002.
There are a couple of other parameters that we did not modify, but which you
should be aware of in an enterprise deployment environment:
xend-relocation-address: This is a flag for restricting the migration of the
domain only to a specific interface. The address specified is the one that
listens for connections coming into the relocation socket. This flag will only
be used if you also enable the xend-relocation-server parameter.
xend-relocation-hosts-allow: This is a flag that defines the hosts that are
allowed to communicate with the relocation port. The value is a sequence
of regular expressions separated by spaces. If the value is empty, then all
incoming connections are allowed. The values can match either an IP address
or a fully qualified domain name.
???
???
???
???
Migration
[ 120 ]
The discussion and diagram in this section of how Xen's live migration feature works
is based on the excellent research papers by the Xen team, which are available at
http://www.
Pages:
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112