Changes

Jump to: navigation, search

Migrating Xen domainU Guests Between Host Systems

53 bytes added, 18:52, 29 May 2016
m
Text replacement - "<htmlet>xen<htmlet>" to "<htmlet>xen</htmlet>"
</table>
<hr>
 
 
<htmlet>xen</htmlet>
</pre>
Secondly, the ''xend-relocation-hosts-allow'' value must be changed to define the hosts from which relocation requests will be accepted. This can be a list of hostnames or IP addresses including wildcards. An empty value may also be specified (somewhat insecurely) to accept connections from any host. The following example allows migration requests only from a host with the Ip an IP address of 192.168.2.20:
<pre>
</pre>
In order to resolve this problem it is essential that the firewall on the destination host be configured to allow TCP traffic on either port 8002 or , if the default value was not used, the port number specified for ''xend-relocation-port'' in the ''/etc/xen/xend-config.sxp'' files if the default value was not usedfile.
== Preparing the Xen Migration Environment ==
The next requirement for performing live migrations involves the creation of a Xen domainU guest to migrate. For the purposes of this chapter, we will use a disk image based domainU guest environment installed in the ''/xen'' directory of a server. The steps required to create such a guest are outlined in detail in the chapter entitled [[Building a Xen Virtual Guest Filesystem on a Disk Image (Cloning Host System)]], which will instruct you provides steps on how to create and configure the following files:
<pre>
== Checking the Xen Log for Migration Errors ==
The migration from a user's perspective is a silent process. This can make tracking down problems difficult since a failed migration will often not report anything on the command-line. If problems are encountered during the migration the first place to look for information is the Xen log file which can be viewed by running the ''xm log'' command. The following shows partial output from a successful live migration:
<pre>
VmError: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 248744 KiB free.
</pre>
 
 
<htmlet>xen</htmlet>

Navigation menu