[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] XCP - grace arp missing while migrating VM


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Thu, 22 Jul 2010 02:04:39 +0400
  • Delivery-date: Wed, 21 Jul 2010 15:07:45 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=PaclNl3UoZyl42FTk7vvYSdqVUeR+nRW98+Oh0ac+YTIYSDqUP5vipHxInvUhj6EM8 0Kvaw/2dyXoa5pIhj8IeIcM7rFDbGYdlJqpnoOt4FH4hX0Oh2NBfP0a/T+iycwLADHIT uzkjnXZfjuw2SBfE4/x3PUa78RHIYR7zvu8AY=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

This problem was actual even in XCP 0.11, and now I confirm it in XCP
0.5.

When idle VM migrating between hosts no any arp requests sends on behave
of VM (or from guest kernel), so for few minutes (depends on settings of
switches in network) VM become inaccessible via IP.

More specific:

Scheme (monospace fonts):

Before migration:
+-----------+
|           | ---port1 ----[HOST1  (VM) ]
|L2 switch  |
|           |----port2 ----[HOST2]
+-----------+

After:
+-----------+
|           | ---port1 ----[HOST1 ]
|L2 switch  |
|           |----port2 ----[HOST2 (VM) ]
+-----------+

When VM boots on host1 it send arp packet to neighbors and switch learn
that any traffic to MAC=XX:XX:XX:XX:XX:XX must be sent to port1.

After that, if we migrate vm to host2 and this VM will not sent any data
switch will not learn about  port change and continue to directs all
traffic to mac XX:XX:XX:XX:XX:XX to port1 (and this traffic will
silently ignored by OVS/dom0 kernel).

This will continue until:

1) VM send any packet outside
2) switch decide to update MAC-port table


This is real problem: in my test debian without any network services
does not sent any data outside within hours, and switch does not update
table often. 

How it can be fixed?

I see two ways:
1) dom0 in host2 sent fake arp packet after accepting migrating VM
(single packet does not create any problem to anyone). In this case dom0
controls 'network migration' process

2) domU after receiving event about migration initiate arp broadcast
message.

I don't know which way  is better (#1 seems for me more controllable),
but without those actions migration will cause sometime illusion of VM
hang (no reply to pings).

---
wBR, George.


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.