[Xen-devel] Migration : network latency due to ARP Reply not generated

[Olivier Blanc <olivier.blanc@xxxxxxxxxxxxxxxxxxxxxx>]

Hi, 
I really need help, as I am stuck !

I am working with Xen 3.3.1 on OpenSuse 11 with 2.6.24 kernel

My network is bridged over vlan.
When I migrate a DOMU (fedora core), the ARP REPLY Non Sollicited is not generated so I have a long network latency before my DOMU becomes reachable.
What am i doing wrong so that Xen does not generate the ARP ?

Here is my bridge configuration (stp is off) :

admin
 bridge id		8000.001a6452105c
 designated root	8000.001a6452105c
 root port		   0			path cost		   0
 max age		  20.00			bridge max age		  20.00
 hello time		   2.00			bridge hello time	   2.00
 forward delay		   0.00			bridge forward delay	   0.00
 ageing time		 300.01
 hello timer		   0.49			tcn timer		   0.00
 topology change timer	   0.00			gc timer		   0.49
 flags			


eth0.2 (1)
 port id		8001			state		     forwarding
 designated root	8000.001a6452105c	path cost		 100
 designated bridge	8000.001a6452105c	message age timer	   0.00
 designated port	8001			forward delay timer	   0.00
 designated cost	   0			hold timer		   0.00
 flags			

tap18.0 (2)
 port id		8002			state		     forwarding
 designated root	8000.001a6452105c	path cost		 100
 designated bridge	8000.001a6452105c	message age timer	   0.00
 designated port	8002			forward delay timer	   0.00
 designated cost	   0			hold timer		   0.00
 flags			

vif18.0 (3)
 port id		8003			state		     forwarding
 designated root	8000.001a6452105c	path cost		 100
 designated bridge	8000.001a6452105c	message age timer	   0.00
 designated port	8003			forward delay timer	   0.00
 designated cost	   0			hold timer		   0.00
 flags			

Here are the configuration of my ETH0 interface and vlan interface
sv1:~ # ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:1A:64:52:10:5C  
          inet adr:172.1.0.1  Bcast:172.1.0.255  Masque:255.255.255.0
          adr inet6: fe80::21a:64ff:fe52:105c/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1807086 errors:0 dropped:680 overruns:0 frame:0
          TX packets:2458143 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:1808257592 (1724.4 Mb)  TX bytes:2957025946 (2820.0 Mb)
          Interruption:24 

sv1:~ # ifconfig eth0.2
eth0.2    Link encap:Ethernet  HWaddr 00:1A:64:52:10:5C  
          adr inet6: fe80::21a:64ff:fe52:105c/64 Scope:Lien
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0 
          RX bytes:600 (600.0 b)  TX bytes:4828 (4.7 Kb)

BTW, xm vnet-list never return real information of bridges is that normal ?
sv1:~ # xm vnet-list -l
"{'Status': 'Failure', 'ErrorDescription': ['MESSAGE_METHOD_UNKNOWN', 'xend_vnet']}"
"{'Status': 'Failure', 'ErrorDescription': ['MESSAGE_METHOD_UNKNOWN', 'xend_vnet']}"


Thanks for help

Olivier


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