Xen users - Jun 2009 - Network faillure after domU migration

Hi all,
I am using xen 3.1.0 on debian Lenny, installed by using debian packets.
You will see the out put of the "xm info" command at the end of this
mail.

I configure xen to use route mode for network. domUs have private adress
(1.0.0.1). The communication between domU woks perfectly. I use iptables
command to make this communication possible.

I write a simple network bench in C language which content two program:
client and server. The client and server communicates infinitely and print
their received messages.

The bench work well when I run them. The problem occur after à migration
of a domU. A run the client and the server on different domUs. After à
moment, I initiate a live migration of one domU (for example those which
host the server ). After this migration, the program running on the
migrated domU crash and the bench stop working.

To be completely, befor initiate a migration, I configure the destination
physical machine with iptables commands to route packets for domU. I also
configure client machines dom0 to comunicate route packets to the new
machine (which will receive the domU).

My questions are:
---how does the live migration work in xen for route mode
---in the xen source code, which programm files contents live migration
implementation?

Thank you for your answer.

################################xm_info############################################
release                : 2.6.26-1-xen-686
version                : #1 SMP Sat Jan 10 22:52:47 UTC 2009
machine                : i686
nr_cpus                : 2
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2660
hw_caps                :
bfebfbff:20100000:00000000:00000040:0008e39d:00000000:00000001
total_memory           : 3956
free_memory            : 128
xen_major              : 3
xen_minor              : 1
xen_extra              : .0
xen_caps               : xen-3.0-x86_32p
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xf5800000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.3 20080704 (prerelease) (Debian
4.1.2-25)
cc_compile_by          : root
cc_compile_domain      :
cc_compile_date        : Mon Jan 26 16:08:31 CET 2009
xend_config_format     : 4

###################################################################################

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

Hi all,
I am using xen 3.3.1 on debian Lenny, installed by using debian packets.
You will see the out put of the "xm info" command at the end of this
mail.

I configure xen to use route mode for network. domUs have private adress
(1.0.0.1). The communication between domU woks perfectly. I use iptables
command to make this communication possible.

I write a simple network bench in C language which content two program:
client and server. The client and server communicates infinitely and print
their received messages.

The bench work well when I run them. The problem occur after à migration
of a domU. A run the client and the server on different domUs. After à
moment, I initiate a live migration of one domU (for example those which
host the server ). After this migration, the program running on the
migrated domU crash and the bench stop working.

To be completely, befor initiate a migration, I configure the destination
physical machine with iptables commands to route packets for domU. I also
configure client machines dom0 to comunicate route packets to the new
machine (which will receive the domU).

My questions are:
---how does the live migration work in xen for route mode
---in the xen source code, which programm files contents live migration
implementation?

Thank you for your answer.

################################xm_info############################################
release                : 2.6.26-1-xen-686
version                : #1 SMP Sat Jan 10 22:52:47 UTC 2009
machine                : i686
nr_cpus                : 2
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2660
hw_caps                :
bfebfbff:20100000:00000000:00000140:0008e39d:00000000:00000001:00000000
virt_caps              :
total_memory           : 3956
free_memory            : 128
node_to_cpu            : node0:0-1
node_to_memory         : node0:128
xen_major              : 3
xen_minor              : 3
xen_extra              : .1
xen_caps               : xen-3.0-x86_32p
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xf5800000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.3.3 (Debian 4.3.3-10)
cc_compile_by          : root
cc_compile_domain      : cluster-astre-tune.fr
cc_compile_date        : Fri Jun  5 09:48:09 CEST 2009
xend_config_format     : 4

###################################################################################



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

Hello,

Am 05.06.2009 um 11:31 Uhr schrieb Alain.Tchana@enseeiht.fr:
[..]
> My questions are:
> ---how does the live migration work in xen for route mode
on both dom0s the network of the domU must be known and must be routed from 
outside correctly. I''m not sure if this is possible! Use bridged mode
if you
want to use live migration!
If this is a limitation, this not a limition of xen but of ip networking.


-- 
greetings

eMHa


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