From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Kamil Rytarowski" <kamil@netbsd.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PULL v3 10/15] tests/vm/netbsd: Disable IPv6
Date: Fri, 25 Oct 2019 20:37:04 +0100 [thread overview]
Message-ID: <20191025193709.28783-11-alex.bennee@linaro.org> (raw)
In-Reply-To: <20191025193709.28783-1-alex.bennee@linaro.org>
From: Eduardo Habkost <ehabkost@redhat.com>
Workaround for issues when the host has no IPv6 connectivity.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20191018181705.17957-4-ehabkost@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
diff --git a/tests/vm/netbsd b/tests/vm/netbsd
index ee9eaeab504..18aa56ae826 100755
--- a/tests/vm/netbsd
+++ b/tests/vm/netbsd
@@ -28,6 +28,13 @@ class NetBSDVM(basevm.BaseVM):
gmake --output-sync -j{jobs} {target} {verbose};
"""
+ # Workaround for NetBSD + IPv6 + slirp issues.
+ # NetBSD seems to ignore the ICMPv6 Destination Unreachable
+ # messages generated by slirp. When the host has no IPv6
+ # connectivity, this causes every connection to ftp.NetBSD.org
+ # take more than a minute to be established.
+ ipv6 = False
+
def build_image(self, img):
cimg = self._download_with_cache("http://download.patchew.org/netbsd-7.1-amd64.img.xz",
sha256sum='b633d565b0eac3d02015cd0c81440bd8a7a8df8512615ac1ee05d318be015732')
--
2.20.1
next prev parent reply other threads:[~2019-10-25 20:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 19:36 [PULL v3 00/15] testing updates Alex Bennée
2019-10-25 19:36 ` [PULL v3 01/15] travis.yml: reduce scope of the --enable-debug build Alex Bennée
2019-10-25 19:36 ` [PULL v3 02/15] travis.yml: Add libvdeplug-dev to compile-test net/vde.c Alex Bennée
2019-10-25 19:36 ` [PULL v3 03/15] travis.yml: Use libsdl2 instead of libsdl1.2, and install libsdl2-image Alex Bennée
2019-10-25 19:36 ` [PULL v3 04/15] travis.yml: Use newer version of libgnutls and libpng Alex Bennée
2019-10-25 19:36 ` [PULL v3 05/15] travis.yml: Fix the ccache lines Alex Bennée
2019-10-25 19:37 ` [PULL v3 06/15] travis.yml: Test the release tarball Alex Bennée
2019-10-25 19:37 ` [PULL v3 07/15] travis.yml: bump Xcode 10 to latest dot release Alex Bennée
2019-10-25 19:37 ` [PULL v3 08/15] cirrus.yml: add latest Xcode build target Alex Bennée
2019-10-25 19:37 ` [PULL v3 09/15] tests/vm: Let subclasses disable IPv6 Alex Bennée
2019-10-25 19:37 ` Alex Bennée [this message]
2019-10-25 19:37 ` [PULL v3 11/15] travis.yml: cache the clang sanitizer build Alex Bennée
2019-10-25 19:37 ` [PULL v3 12/15] gitlab-ci.yml: Use libvdeplug-dev to compile-test the VDE network backend Alex Bennée
2019-10-25 19:37 ` [PULL v3 13/15] travis.yml: --enable-debug-tcg to check-tcg Alex Bennée
2019-10-25 19:37 ` [PULL v3 14/15] tests/docker: set HOST_ARCH if we don't have ARCH Alex Bennée
2019-10-25 19:37 ` [PULL v3 15/15] tests/docker: update Travis image to a more current version Alex Bennée
2019-10-27 19:39 ` [PULL v3 00/15] testing updates Peter Maydell
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=20191025193709.28783-11-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=kamil@netbsd.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).