Bug#868242: open-vm-tools: VMXNET3 network interface hard locks VM after Vmware hw v8 to hw v13

[Ben Hutchings]

Control: tag -1 moreinfo

On Thu, 13 Jul 2017 17:55:40 +0200 Bernd Zeimetz  wrote:
> reassign 868242 src:linux
> thanks
> 
> hi,
> 
> open-vm-tools has pretty much nothing to do with the vmxnet3 module.
> The module is shipped with the kernel.
> 
> Therefore I'll reassign this bug to the kernel.
> 
> Also you should open a case at vmware, they maintain the kernel
> modules upstream and they are the only people who can debug this issue.
[...]

This actually sounds a bit like an ESX bug:
https://bugzilla.kernel.org/show_bug.cgi?id=191201

Can you check whether either of the workarounds works for you? 
Apparently you can put this in the VMSS file:

vmxnet3.rev.30 = FALSE

or run this in the guest, substituting the network interface name:

ethtool -G  rx-mini 0

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.


signature.asc
Description: This is a digitally signed message part

Bug#868242: open-vm-tools: VMXNET3 network interface hard locks VM after Vmware hw v8 to hw v13

[Bernd Zeimetz]

reassign 868242 src:linux
thanks

hi,

open-vm-tools has pretty much nothing to do with the vmxnet3 module.
The module is shipped with the kernel.

Therefore I'll reassign this bug to the kernel.

Also you should open a case at vmware, they maintain the kernel
modules upstream and they are the only people who can debug this issue.

Best regards,

Bernd


--
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#868242: open-vm-tools: VMXNET3 network interface hard locks VM after Vmware hw v8 to hw v13

[Matt Weatherford]

Package: open-vm-tools
Version: 2:10.1.5-5055683-4
Severity: normal

Dear Maintainer,


   * What led up to the situation?

Debian 9 vm working fine on HW version 8 for months using VMXNET3 network 
interface
In VMWare virtualcenter Server, VM on ESXi running VMWare 6.5, I upgraded VM 
hardware from verson 8
to version 13.

Network interface worked ok for a a while, then sporadically disconnected from 
the network for 5-20 minutes, 
eventually hard-locking the vm
 

   * What exactly did you do (or not do) that was effective (or
 ineffective)?


I powered down the VM, deleted the VMXNET3 network interface, and added back a 
E1000 network interface.
The system has been up now without problems for 15 hours


Not sure if this is the place for this package- not sure where the VMXNET3 
driver lives - maybe that is
a remnant left over from an old VMware tools install that I did then disbled in 
favor of open-vm-tools ?

Unclear where all the parts live.  Apologies if this is user error.

Thank you for supporting Debian!

-Matt W
Seattle, WA


-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages open-vm-tools depends on:
ii  init-system-helpers1.48
ii  iproute2   4.9.0-1
ii  libc6  2.24-11+deb9u1
ii  libdumbnet11.12-7+b1
ii  libfuse2   2.9.7-1
ii  libgcc11:6.3.0-18
ii  libglib2.0-0   2.50.3-2
ii  libicu57   57.1-6
ii  libmspack0 0.5-1+b2
ii  libprocps6 2:3.3.12-3
ii  libssl1.0.21.0.2l-2
ii  libstdc++6 6.3.0-18
ii  libxerces-c3.1 3.1.4+debian-2
ii  libxml-security-c17v5  1.7.3-4
ii  pciutils   1:3.5.2-1

Versions of packages open-vm-tools recommends:
ii  ethtool  1:4.8-1+b1
ii  fuse 2.9.7-1
ii  lsb-release  9.20161125
ii  zerofree 1.0.4-1

Versions of packages open-vm-tools suggests:
pn  cloud-init 
pn  open-vm-tools-desktop  

-- Configuration Files:
/etc/vmware-tools/tools.conf changed:


-- no debconf information