From: Craig MacKinder <craig@blueshift.net>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Nameserver lookups fail on virtual server after Kernel upgrade from version 4.9 to 4.12
Date: Sat, 19 Aug 2017 22:15:12 +0000 [thread overview]
Message-ID: <222B490D-DD8F-4DE6-A9F0-B2042231F68C@blueshift.net> (raw)
In-Reply-To: <e4bc0bb6-60c8-da2e-686b-8bb5a8af2917@monksofcool.net>
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
It sounds like this vmxnet3 bug causing intermittent interface problems
https://bugzilla.kernel.org/show_bug.cgi?id=191201
Try adding this to the VMware guest advanced settings.
vmxnet3.rev.30 = FALSE
And restart the guests.
--
Craig
On Aug 19, 2017, at 11:28 AM, Ralph Seichter <m16+gentoo@monksofcool.net<mailto:m16+gentoo@monksofcool.net>> wrote:
It seems strange to me as I write it, but since I updated one of my
virtual servers from Kernel version 4.9.34 to 4.12.5, the server (Gentoo
Linux running as a KVM guest) is experiencing timeouts when trying to
connect to DNS resolvers. For the Kernel update, I followed the same
steps I used for years, like
cd /usr/src/linux
zcat /proc/config.gz >.config
make silentoldconfig (answering "no" whereever possible)
make ...
After booting with Kernel 4.12, commands like "dig +trace www.ibm.com<http://www.ibm.com>"
work just fine for a while, duration depending on server load, but after
some threshold is passed, all further attempts to contact resolvers fail
due to timeouts.
I have tried running a local, caching resolver (BIND 9) on the server,
like I usually do, and also tried using the hoster's dedicated resolvers.
With Kernel 4.12, I see timeouts in both cases. These problems do not
occur when I boot with the 4.9 Kernel which I have been using for the
past two months.
It is also worth noting that I updated two other servers to Kernel 4.12
without any issues, but these are "real" servers, not VMs. At this point
I am searching for ways to debug the issue, vaguely suspecting some KVM
magic behind it (without any proof). I know that Kernel 4.11 introduced
several KVM related changes, but that's about it.
I appreciate all pointers.
-Ralph
[-- Attachment #2: Type: text/html, Size: 2829 bytes --]
next prev parent reply other threads:[~2017-08-19 22:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 18:28 [gentoo-user] Nameserver lookups fail on virtual server after Kernel upgrade from version 4.9 to 4.12 Ralph Seichter
2017-08-19 22:15 ` Craig MacKinder [this message]
2017-08-19 23:14 ` Ralph Seichter
2017-08-20 6:17 ` Neil Bothwick
2017-08-20 12:25 ` Ralph Seichter
2017-08-21 6:08 ` Neil Bothwick
2017-08-21 10:35 ` Ralph Seichter
2017-08-21 11:49 ` [gentoo-user] install under centos606 mad.scientist.at.large
2017-08-21 12:08 ` Ralph Seichter
2017-08-23 3:18 ` R0b0t1
2017-08-21 13:03 ` Zhu Sha Zang
2017-08-21 19:18 ` Mick
2017-08-22 5:21 ` Stroller
2017-08-23 3:21 ` R0b0t1
2017-08-21 18:29 ` [gentoo-user] Nameserver lookups fail on virtual server after Kernel upgrade from version 4.9 to 4.12 Mick
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=222B490D-DD8F-4DE6-A9F0-B2042231F68C@blueshift.net \
--to=craig@blueshift.net \
--cc=gentoo-user@lists.gentoo.org \
/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