Workstation Pro 12.5.6 build-5528349 crashes on several Linux based software image

[Bascisco]

Hello Community,

As i can't log a support ticket to VMware I am reporting this via the community.

I have a Lenovo P50 machine with 1TB SSD and 64GB DRAMM.

I am running for a long while some company specific linux based software (we have OVA files)
Since the upgrade to 12.5.6 build-5528349 I experience crashes of the VMware instances.

I have log files of that which I can only share with VMware direct and not to a forum like this.

However I would like to hear if others reported crash upgrading to 12.5.6 build-5528349.

I can from version 12.5.5

Brgds,

B

as.

[dariusd]

I've sent you a private message with an invitation to send me your logs off-forum.  Please let me know if you've received it!

My generic initial troubleshooting questions would be: (1) What's the nature of the crash, or at least an error message?  (2) Does it go away if you downgrade to Workstation 12.5.5 again?  (3) What's your host OS (including kernel/version/build number)?

Cheers,

--

Darius

[Bascisco]

Hello Darius,

Thank you for getting back to me. As others might still read the post. I have one question on the downgrade you suggested.

As my upgrade where till this point via  WS Workstation upgrade process.

I tried to downgrade using, VMware-workstation-full-12.5.5-5234757.exe that I downloaded from the VMware site. Then I got this message executing that file.

Please do not tell me that I have to uninstall VMware Workstation. Because Then I have to set up all my 19 vmnets again.

Hence how can I save that and to remaining other settings. Then a downgrade isn't a pain.

Thanks again for the fast response.

Bas.

[continuum]

Make a backup of current setting in all your configured vmnets	vnetlib64.exe -- export backup-file-name
Restore vmnet-settings from a backup	vnetlib64.exe -- import backup-file-name

that used to work in the pre-china-releases.
By the way - I would highly recommend to always use this sequence:
- uninstall current version
- reboot
- check registry for items that failed to uninstall and delete them manually
- reboot
- install different version.
Just using the upgrade-function is IMHO an unacceptable risk.
Ulli

[Bascisco · Accepted solution]

Hello Darius,

Your remark of MTU 1600 triggered it for me. Indeed not the upgrade as such. Although IMHO VMware image shouldn't crash on it, but you mentioned that already ;-).

I had from a config template indeed mtu set to 1600.

I changed that to mtu 1536 and even with now again dot1q on it works. And no more VMWare crashes either.

I want to have a minimal payload of 1500 IP bytes + 20 bytes IP header + 8 bytes dot1q +  (2 * 4 bytes MPLS label) makes 1536 as minimum for the L2 Ethernet frame.

I changed that and even all works for the B2B directly connected working interface, redundancy interface I will see later back for the other interfaces that will also run MPLS between each other.

So for others remember this one regarding MTU Size do not pass beyond 1600 or VMware  Workstation crashes due the vmxnet3 driver.

Thank you again for your help.