@fipsy wrote:
Yes, even with version 16.2.2 build-19200509 the problem still exists in different scenarios. If it takes too long until a paused machine is resumed, the error occurs. The same applies if the disk is compressed in a Linux machine (vmware-toolbox-cmd disk shrink /). Even the workaround
isolation.tools.hgfs.oplockmonitor.enable = "FALSE"
does not help in this case. Only
mks.sandbox.socketTimeoutMS = "1000000"
helps.
By Linux machine, you are referring to the virtual machine and not the host, right?
When you set the above setting in the virtual machine's VMX file, it was powered off at the time, right?
The issue described and addressed by the workaround only applies to Windows hosts.
If the workaround does not prevent your issue, then you are running into a different issue, possibly with similar symptoms.
If you hit the issue do the following:
- Start the Task Manager
- Select the Details tab
- Find and select the vmware-vmx.exe process for your virtual machine.
- Right-click and select "Analyze Wait Chain"
Report here the details of the dialog box shown.
(See Wait Chain Traversal for more details.)
Thanks.
Steve
