Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #188020

Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised"

From Nicholas Geovanis <nickgeovanis@gmail.com>
Newsgroups linux.debian.user
Subject Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised"
Date 2017-10-18 18:10 +0200
Message-ID <uBZ4S-3kn-19@gated-at.bofh.it> (permalink)
References <uBY8P-2JJ-39@gated-at.bofh.it> <uBYs9-2Qk-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Wed, Oct 18, 2017 at 10:26 AM, Sven Hartge <sven@svenhartge.de> wrote:

> Nicholas Geovanis <nickgeovanis@gmail.com> wrote:
>
> > kernel: TCP: ens192: Driver has suspect GRO implementation, TCP
> > performance may be compromised
>


> As long as you use at lease ESXi 6.5u1 there will be no problem. If you
> are on pre-6.5u1, your Stretch VMs will freeze/crash after a short amount
> of
> traffic because of a bug in those earlier ESXi releases.
>

Thanks Sven, I later ran across the bugzilla. Unfortunately we are at ESXi
5.5 for at least the rest of the year, so that route is closed for now.

Have you tried the "ethtool WXYZ -G rx-mini 0" workaround?
I receive messages:
rx-mini unmodified, ignoring
no ring parameters changed, aborting

However ethtool reports that rx-mini is already 0:
root@saltlab05:~# ethtool -g ens192
Ring parameters for ens192:
Pre-set maximums:
RX:             4096
RX Mini:        0
RX Jumbo:       4096
TX:             4096
Current hardware settings:
RX:             256
RX Mini:        0
RX Jumbo:       128
TX:             512

Have you tried the vmx file change?
vmxnet3.rev.30 = FALSE

Vielen Dank.....Nick G


> See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864642
> https://www.reddit.com/r/homelab/comments/6s5dh6/debian_9_on_esxi_65u1_
> complete_lockup/
> https://bugzilla.kernel.org/show_bug.cgi?id=191201#c49
>
> Grüße,
> Sven.
>

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-18 17:10 +0200
  Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" Sven Hartge <sven@svenhartge.de> - 2017-10-18 17:30 +0200
    Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-18 18:10 +0200
      Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" Sven Hartge <sven@svenhartge.de> - 2017-10-18 18:40 +0200
        Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-19 19:00 +0200
          Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" deloptes <deloptes@gmail.com> - 2017-10-19 19:50 +0200
            Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-19 20:30 +0200
          Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" Sven Hartge <sven@svenhartge.de> - 2017-10-19 20:30 +0200
            Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-19 21:00 +0200
              Re: Debian 9.2, VSphere 6.5.0, "TCP performance may be compromised" Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-19 21:20 +0200

csiph-web