WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Arp not sent after live migrations on xen-unstable

Subject: Re: [Xen-users] Arp not sent after live migrations on xen-unstable
From: Nathan March <nathan@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 23 Aug 2010 14:49:57 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 23 Aug 2010 14:51:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C6EBC0D.8040000@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4C6C4F29.5090402@xxxxxxxxxxxxxxxxxxxx> <1282179225.29131.3.camel@xxxxxxxxxxxxxxxx> <4C6D65C8.20303@xxxxxxxxxxxxxxxxxxxx> <1282304746.6269.4.camel@xxxxxxxxxxxxxxxxxxxxx> <4C6EBC0D.8040000@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
Fwiw, this problem was due to me manually creating the bridge instead of letting xen do it, like the libvirt docs recommend. I've dropped the manual bridge and gone back to the xen scripts and things work fine now.

- Nathan

On 8/20/2010 10:31 AM, Nathan March wrote:
Thanks for the info George, I'm going to assume it's something I've done and start from scratch.

- Nathan

On 8/20/2010 4:45 AM, George Shuklin wrote:
Good day.

I found that newer version of kernel (2.6.34-xen) from gentoo (wich one
is stealed somewere (suse? not sure)) adopted to debian works fine.

At least within my tests (4 cycles of migration between every of 6
testings servers) I was unable to reproduce bugs.

I'll continue to tests, if I was wrong and bug still exists, I'll mail
about this.

PS Migration tested on XCP 0.5 by xe vm-migrate command.

В Чтв, 19/08/2010 в 10:11 -0700, Nathan March пишет:
The consensus from the mailing list posts I found a while ago seemed
to imply that it had been fixed so I'm not clear if this is an
outstanding bug, a regression or just something that I'm doing wrong
that has broken it.

Are there any steps I can take to debug this further and try and get
some more info? Cranking up the debug level on xend didn't seem to
result in anything useful.

- Nathan

On 8/18/2010 5:53 PM, George Shuklin wrote:
I'm pretty concerned about this problem.

Right now: I suppose, it was fixed somewhere in new netfront driver.
(not checked).

If no, I have few ideas about workaround. Main is an event via xen-evtch about suspending. Small module/appilcation in guest can sent a fake ARP every time it got suspend event. Other is using xenstore to send command
to program from host. (both are ugly hacks).

Best way is still fake ARP from netback or netfront...

В Срд, 18/08/2010 в 14:22 -0700, Nathan March пишет:
Hi All,

Having an issue with xen-4.0-unstable where after completing a live
migration, an arp is never sent out to update the switch with the new
location of the mac address.

Network is configured as per libvirt's instructions with the xen
network-script disabled and the bridge (xenbr0) always up.
http://wiki.libvirt.org/page/Networking#Bridged_networking_.28aka_.22shared_physical_device.22.29

Things work fine 10s after doing the migration once the switch has
picked up the move, checking the mac address tables confirms it's still
going to the old host. I've also confirmed that it's not going out at
all via a span port on the switch.

Saw a bunch of postings a while ago regarding it, but nothing recent.
Anyone have any insight on what might be wrong?

- Nathan

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

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


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

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

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