From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [xen-4.0-testing test] 2045: regressions - FAIL
Date: Thu, 26 Aug 2010 08:06:30 +0100 [thread overview]
Message-ID: <1282806390.3469.22.camel@localhost.localdomain> (raw)
In-Reply-To: <19573.24591.154634.863643@mariner.uk.xensource.com>
On Wed, 2010-08-25 at 19:25 +0100, Ian Jackson wrote:
>
>
> test-amd64-i386-pair 12 guest-migrate/src_host/dst_host fail REGR.
> vs. 1993
>
> It seems that PV migration of a domain from one host to another
> doesn't work properly. Looking at the logs everything is absolutely
> fine except that the domU isn't responding to arps and pings for at
> least the 20s that the test system waits 20s after migration.
This is with a PVops domU kernel? If so then I'm surprised this is a
regression rather than a never passed. Until very recently a pvops
kernel would not even attempt to send a gratuitous ARP after a
migration, which could lead to 20-30s timeouts like this. (I suppose it
might spuriously pass if a test run got very lucky?)
This was fixed in v2.6.36-rc1 and was backported to stable kernel
v2.6.32.19 and various v2.6.(>32).y as well.
Even with the fix in place the gratuitous ARP behaviour is disabled by
default so you need to enable the net.ipv4.conf.<dev>.arp_notify sysctl
for any device you want to send the notifications. When I was testing I
did this by adding
net.ipv4.conf.default.arp_notify = 1
to /etc/sysctl.conf and that seemed to do the trick.
(remember that we are testing 2.6.32.18 at the moment until 2.6.32.21 is
out)
Ian.
next prev parent reply other threads:[~2010-08-26 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 14:21 [xen-4.0-testing test] 2045: regressions - FAIL xen.org
2010-08-25 15:40 ` Pasi Kärkkäinen
2010-08-25 18:25 ` Ian Jackson
2010-08-26 7:06 ` Ian Campbell [this message]
2010-08-31 14:35 ` Ian Jackson
2010-08-31 15:05 ` Ian Campbell
2010-08-31 15:10 ` Ian Jackson
2010-08-31 18:11 ` Ian Jackson
2010-08-31 18:49 ` Ian Campbell
2010-09-17 14:09 ` Jan Beulich
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=1282806390.3469.22.camel@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).