Bug 473408 - Prolonged network blackout during migration of RHEL 4.7
Summary: Prolonged network blackout during migration of RHEL 4.7
Keywords:
Status: CLOSED DUPLICATE of bug 460874
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel-xen
Version: 4.7
Hardware: All
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-28 11:22 UTC by Ian Campbell
Modified: 2008-12-01 17:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-01 17:08:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Use register_netdevice_notifier not register_inetaddr_notifier (1.21 KB, patch)
2008-11-28 11:22 UTC, Ian Campbell
no flags Details | Diff

Description Ian Campbell 2008-11-28 11:22:12 UTC
After a live migration of a 2.6.9-78.EL kernel we are seeing network blackouts on the order of several minutes. It appears that the gratuituous ARP is not being sent at all.

In 2.6.9-72.EL RHEL 4 bug #444473 was closed after applying the patch from #441716 comment #5 however #441716 comment #6 points out that this doesn't work due to "silly cut and paste errors" and proposes an updated patch instead, this is the one which is in RHEL 5 currently. I've patched in the difference between the two (basically turning register_inetaddr_notifier into  register_netdevice_notifier) onto 2.6.9-78.0.5.EL and it seems to repair things.

Comment 1 Ian Campbell 2008-11-28 11:22:56 UTC
Created attachment 324981 [details]
Use register_netdevice_notifier not register_inetaddr_notifier

Comment 3 Herbert Xu 2008-11-28 12:35:10 UTC
Already fixed in 78-15.  As to whether the fix will make it to RHEL4.7 I'm afraid I'm qualified to answer.

Comment 4 Ian Campbell 2008-11-28 13:40:40 UTC
Thanks. Is there a bugzilla entry already? I searched before I filed this but didn't find it.

Comment 5 Don Dutile (Red Hat) 2008-12-01 17:08:54 UTC
the bz that fixed this problem is 460874.

It is being backported to the 4.7-z stream release under bz 469891.

Closing this bz as a dupe of 460874 & 469891.

- Don

*** This bug has been marked as a duplicate of bug 460874 ***


Note You need to log in before you can comment on or make changes to this bug.