Bug 1471532 - Workstation completely frozen when using ESXi and VMXNET3 adapter
Summary: Workstation completely frozen when using ESXi and VMXNET3 adapter
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: open-vm-tools
Version: 27
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ronak Doshi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-16 17:33 UTC by Alessandro
Modified: 2018-06-25 22:28 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-25 22:28:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alessandro 2017-07-16 17:33:54 UTC
Description of problem:

I have Fedora Workstation 26 (issue found on 25 too) running on ESXi 6.5 on a Xeon-D processor. I am using the LXDE spin.
When using VMXNET3 as network adapter, the VM sometimes freezes and becomes completely unresponsive: the UI freezes, cannot connect via SSH, etc. Forcing a hard reset of the VM seems to be the only possibility.
The crash happens "randomly", but an action that causes it to happen every time is to visit "speedtest.net" using Google Chrome (no issue with Midori, however).
Changing adapter to E1000e solves the problem.



Steps to Reproduce:

Can happen randomly, but a way to trigger it any time:
1. Install Google Chrome
2. Visit speedtest.net

Note: I've noticed the crash also when not using Google Chrome, randomly. I am not able to find another way to reproduce the issue 100% of the times.


Actual results:

System completely frozen and requires a hard reset. UI is frozen, can't connect via SSH, etc.



Expected results:

System should work as normal.


Additional info:

Using Fedora 26 as Workstation (same issue on 25). Using the LXDE spin.

Comment 1 Fedora End Of Life 2018-05-03 07:51:05 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Ravindra Kumar 2018-05-03 22:32:07 UTC
Sorry to have missed this earlier. This is not really open-vm-tools issue because VMXNET3 driver is part of Linux kernel now.

Could you please confirm if you are still seeing this with latest Fedora, so that I can bring it to the attention of appropriate folks?

Comment 3 Fedora End Of Life 2018-05-29 12:12:02 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Ravindra Kumar 2018-05-31 00:21:50 UTC
Ronak, could you please help investigate this? Thanks!

Comment 5 Ravindra Kumar 2018-05-31 00:25:34 UTC
Ronak, re-opening this because it might still be an issue. Please verify with different versions of Fedora before drawing any conclusion.

Comment 6 Jan Kurik 2018-05-31 09:12:53 UTC
This bug is currently reported against a Fedora version which is already unsuported.
I am changing the version to '27', the latest supported release.

Please check whether this bug is still an issue on the '27' release.
If you find this bug not being applicable on this release, please close it.

Comment 7 Yan Jin 2018-05-31 09:52:07 UTC
I can reproduce the issue with Fedora Workstation 28

Comment 8 Ronak Doshi 2018-05-31 16:33:41 UTC
Could you provide following information?

1. ESX build - Can be found using "vmware -vl" on esx host
2. Output of following on the VM:
   - uname -a
   - cat /etc/*release
   - ethtool -i <interface name>
<interface name> should be vmxnet3 interface

Thanks,
Ronak

Comment 9 Yan Jin 2018-06-01 01:51:40 UTC
(In reply to Ronak Doshi from comment #8)
> Could you provide following information?
> 
> 1. ESX build - Can be found using "vmware -vl" on esx host
[root@cpdbj-330:~] vmware -vl
VMware ESXi 6.5.0 build-4564106
VMware ESXi 6.5.0 GA


> 2. Output of following on the VM:
>    - uname -a
>    - cat /etc/*release
>    - ethtool -i <interface name>
> <interface name> should be vmxnet3 interface
> 
> Thanks,
> Ronak

==========================
[root@pek2-gosv-16-dhcp111 ~]# uname -r
4.16.3-301.fc28.x86_64
[root@pek2-gosv-16-dhcp111 ~]# cat /etc/redhat-release
Fedora release 28 (Twenty Eight)
[root@pek2-gosv-16-dhcp111 ~]# ethtool -i ens192
driver: vmxnet3
version: 1.4.13.0-k-NAPI
firmware-version:
expansion-rom-version:
bus-info: 0000:0b:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

I have filed an internal bug(id=2131323) to track this

Comment 10 Ronak Doshi 2018-06-25 22:28:10 UTC
It is related to hang issue which has been fixed in 6.5u1. Yan has already tried to repro the same issue on 6.5u1 and did not face the issue.

Recommendation will be to upgrade to esx build of 6.5u1 or later.

Thanks,
Ronak


Note You need to log in before you can comment on or make changes to this bug.