From: Paolo Bonzini <pbonzini@redhat•com>
To: Laszlo Ersek <lersek@redhat•com>
Cc: netdev@vger•kernel.org,
"xen-devel@lists•xensource.com" <xen-devel@lists•xensource.com>
Subject: Re: lost gARP after live migration
Date: Tue, 28 Jun 2011 15:03:08 +0200 [thread overview]
Message-ID: <4E09D10C.8010304@redhat.com> (raw)
In-Reply-To: <4E09D0A0.1080107@redhat.com>
On 06/28/2011 03:01 PM, Laszlo Ersek wrote:
> - (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.
Note that watching the backend and reading its information is quite
common. In fact, that's how the state of the backend is observed in the
first place. Of course you cannot write to the backend tree, but you do
not have to do that.
Paolo
next prev parent reply other threads:[~2011-06-28 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 13:01 lost gARP after live migration Laszlo Ersek
2011-06-28 13:03 ` Paolo Bonzini [this message]
2011-06-28 13:33 ` Ian Campbell
2011-06-28 14:14 ` 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=4E09D10C.8010304@redhat.com \
--to=pbonzini@redhat$(echo .)com \
--cc=lersek@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=xen-devel@lists$(echo .)xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox