From: Laszlo Ersek <lersek@redhat.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: netdev@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: lost gARP after live migration
Date: Tue, 28 Jun 2011 15:01:20 +0200 [thread overview]
Message-ID: <4E09D0A0.1080107@redhat.com> (raw)
Hi,
with reference to RHBZ#713585:
It seems when a RHEL-6.1 or F-15 Xen PV guest is live migrated, the
gratuitous ARP packet is not forwarded to the affected "networking
equipment". The netback vif is added to a routed bridge in the host(s)
and external hosts are expeted to have connection to the guest at all
times, no matter the current Xen host.
I experimented a bit with tcpdump, and the gARP does appear on the
netfront interface. It also appears on the host bridge if sufficient
time passes between completing the xenbus handshake and sending the gARP.
When the guest queues eg. three gARPs in rapid succession, a variable
number of them gets lost. (When all such packets disappear, then the
migrated guest becomes invisible to the outside world, until it
initiates network traffic on its own.)
When the guest waits for about half a second before sending (queueing),
the very first gARP packet successfully appears on the host bridge.
I suspect it's a timing race against the netback vif being added to the
host bridge. What would be a good countermeasure?
- Adding two modparams to xen-netfront (gARP requeue count & number of
msecs to wait between queueing the gARPs).
- (Paolo's idea:) watching the "hotplug-status" xenstore node and
sending a single gARP when the watch fires with "connected". This node
belongs to the backend xenstore subtree, thus watching it from the guest
doesn't please the architecture astronaut in me.
- Something else.
Sorry for the naivety / verbiage.
Thanks,
lacos
next reply other threads:[~2011-06-28 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 13:01 Laszlo Ersek [this message]
2011-06-28 13:03 ` lost gARP after live migration Paolo Bonzini
2011-06-28 13:33 ` Ian Campbell
2011-07-11 14:22 ` [PATCH] xen-netfront: delay gARP until backend switches to Connected Laszlo Ersek
2011-07-12 18:19 ` Konrad Rzeszutek Wilk
2011-07-13 11:44 ` [PATCH v2] " Laszlo Ersek
2011-07-13 13:29 ` Konrad Rzeszutek Wilk
2011-07-13 16:11 ` [PATCH v3] " Laszlo Ersek
2011-07-14 7:44 ` Ian Campbell
2011-06-28 14:14 ` lost gARP after live migration Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E09D0A0.1080107@redhat.com \
--to=lersek@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.