[Xen-users] how to migrate a vm ?

["tgh" <tianguanhua@xxxxxxxxxx>]

Hi

I have setup xen3.0.2.on two nodes, 

I try to migrate a vm from one to the other ,

I have modified xend-config.sxp ,by uncommenting    (xend-relocation-server yes)   and    (xend-relocation-port 8002)

I put the vm conf file and img file in a  nfs node  which the two xen node can get access to

 

but it does not work with the error as follows

Error: (104, 'Connection reset by peer')

 

Xend.log in the sender node :

[2006-09-13 09:17:43 xend] ERROR (xmlrpclib2:124) (104, 'Connection reset by peer')

Traceback (most recent call last):

  File "/usr/lib/python/xen/util/xmlrpclib2.py", line 103, in _marshaled_dispatch

    response = self._dispatch(method, params)

  File "/usr/lib/python2.3/SimpleXMLRPCServer.py", line 407, in _dispatch

    return func(*params)

  File "/usr/lib/python/xen/xend/XendDomain.py", line 417, in domain_migrate

    sock.recv(80)

error: (104, 'Connection reset by peer')

 

   xend.log in the receiver node:

  [2006-09-13 09:19:58 xend] WARNING (tcp:73) Rejected connection from 10.10.107.1:57983 (10.10.107.1) for port 8002.

 

 

Could anyone help me ?

Thanks in advance

 

/etc/xen/xend-config.sxp

# -*- sh -*-

 

#

# Xend configuration file.

#

 

# This example configuration is appropriate for an installation that

# utilizes a bridged network configuration. Access to xend via http

# is disabled.

 

# Commented out entries show the default for that entry, unless otherwise

# specified.

 

#(logfile /var/log/xend.log)

#(loglevel DEBUG)

 

#(xend-http-server no)

#(xend-unix-server no)

#(xend-tcp-xmlrpc-server no)

#(xend-unix-xmlrpc-server yes)

#(xend-relocation-server no)

(xend-relocation-server yes)

 

#(xend-unix-path /var/lib/xend/xend-socket)

 

# Port xend should use for the HTTP interface, if xend-http-server is set.

#(xend-port            8000)

 

# Port xend should use for the relocation interface, if xend-relocation-server

# is set.

(xend-relocation-port 8002)

 

# Address xend should listen on for HTTP connections, if xend-http-server is

# set.

# Specifying 'localhost' prevents remote connections.

# Specifying the empty string '' (the default) allows all connections.

#(xend-address '')

 

#(xend-address localhost)

 

# Address xend should listen on for relocation-socket connections, if

# xend-relocation-server is set.

# Meaning and default as for xend-address above.

(xend-relocation-address '')

 

# The hosts allowed to talk to the relocation port.  If this is empty (the

# default), then all connections are allowed (assuming that the connection

# arrives on a port and interface on which we are listening; see

# xend-relocation-port and xend-relocation-address above).  Otherwise, this

# should be a space-separated sequence of regular expressions.  Any host with

# a fully-qualified domain name or an IP address that matches one of these

# regular expressions will be accepted.

#

# For example:

#  (xend-relocation-hosts-allow '^localhost$ ^.*\.example\.org$')

#

#(xend-relocation-hosts-allow '')

(xend-relocation-hosts-allow '^localhost$')

 

# The limit (in kilobytes) on the size of the console buffer

#(console-limit 1024)

 

##

# To bridge network traffic, like this:

#

# dom0: fake eth0 -> vif0.0 -+

#                            |

#                          bridge -> real eth0 -> the network

#                            |

# domU: fake eth0 -> vifN.0 -+

#

# use

#

# (network-script network-bridge)

#

 

# Your default ethernet device is used as the outgoing interface, by default.

# To use a different one (e.g. eth1) use

#

# (network-script 'network-bridge netdev=eth1')

#

# The bridge is named xenbr0, by default.  To rename the bridge, use

#

# (network-script 'network-bridge bridge=<name>')

#

# It is possible to use the network-bridge script in more complicated

# scenarios, such as having two outgoing interfaces, with two bridges, and

# two fake interfaces per guest domain.  To do things like this, write

# yourself a wrapper script, and call network-bridge from it, as appropriate.

#

(network-script network-bridge)

 

# The script used to control virtual interfaces.  This can be overridden on a

# per-vif basis when creating a domain or a configuring a new vif.  The

# vif-bridge script is designed for use with the network-bridge script, or

# similar configurations.

#

# If you have overridden the bridge name using

# (network-script 'network-bridge bridge=<name>') then you may wish to do the

# same here.  The bridge name can also be set when creating a domain or

# configuring a new vif, but a value specified here would act as a default.

#

# If you are using only one bridge, the vif-bridge script will discover that,

# so there is no need to specify it explicitly.

#

(vif-script vif-bridge)

 

 

## Use the following if network traffic is routed, as an alternative to the

# settings for bridged networking given above.

#(network-script network-route)

#(vif-script     vif-route)

 

 

 

## Use the following if network traffic is routed with NAT, as an alternative

# to the settings for bridged networking given above.

#(network-script network-nat)

#(vif-script     vif-nat)

 

 

# Dom0 will balloon out when needed to free memory for domU.

# dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.

# If dom0-min-mem=0, dom0 will never balloon out.

(dom0-min-mem 196)

 

# In SMP system, dom0 will use dom0-cpus # of CPUS

# If dom0-cpus = 0, dom0 will take all cpus available

(dom0-cpus 0)

 

# Whether to enable core-dumps when domains crash.

#(enable-dump no)

 

 

 

 

 

 

 

 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users