VMware Communities
c13vmw
Contributor
Contributor

Suspend in Player 15.5 (Windows) runs indefinitely as vmware-vmx.exe writes to disk

I am able to reproduce an issue suspending Linux and Windows VMs in Player 15.5.0-14665864. Can any experts also reproduce it

 

Host environment: Windows 7 Pro ESR, 16GB RAM, 500 GB SSD VMs on primary parition

VMWare Player 15.5.0-14665864

Tested VMs: Red Hat Linux 8.3, Windows 10 Pro x64 1909 

Behaviour to reproduce:

1) Start the VM in Workstation player and allow to progress to login screen.

2) Click Suspend in unity UI

3) Observe "Saving virtual machine state..." remains on-screen, quickly proceeds and then never completes past 99% in the title bar

4) Open Resource Monitor and observe that vmware-vmx.exe continuosly writes to disk under multiple spawned threads

Trying to kill the VMWare processes doesn't succeed. A hard shutdown an restart will allow VMWare Player to be started again with no messages and the VMs appear to still be operational as if properly shutdown.

Tags (3)
0 Kudos
1 Reply
c13vmw
Contributor
Contributor

The tail of the vmx log appears to be indicating the PowerOp completed with successs=1 but the unity UI never updates it visually

.....

2021-02-18T13:16:50.794-05:00| vmx| I005: ConfigCheck: No rules file found. Checks are disabled.
2021-02-18T13:16:50.794-05:00| vmx| I005: changing directory to C:\...Virtual Machines\CentOS8\.
2021-02-18T13:16:50.795-05:00| vmx| I005: Config file: C:\...\Virtual Machines\CentOS8\CentOS8.vmx
2021-02-18T13:16:50.795-05:00| vmx| I005: Vix: [mainDispatch.c:4200]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2021-02-18T13:16:50.795-05:00| vmx| I005: Vix: [mainDispatch.c:4200]: VMAutomation_ReportPowerOpFinished: statevar=2, newAppState=1878, success=1 additionalError=0

0 Kudos