Quantcast
Channel: VMware Communities : All Content - Workstation Player
Viewing all articles
Browse latest Browse all 5660

Power off delay

$
0
0

Hi, I have a problem with vmware player (5.0.1 build-894247, host Windows 7 professional x64) during guests poweroff.

The problem occurs after guest os shutdown (successfully completed) or during hard guest power off using "Player-->Power-->Power Off" with a variable delay (1 to 2 minutes); during this delay vmwre player remains black without messages or errors.

After this delay vmware player returns to the home screen with the list of the available virtual machines.

 

I checked guests log searching for some clues and I found some interesting log record on vmware.log, here an example

 

2013-01-11T18:28:07.435+01:00| vmx| I120: MKS PowerOff
2013-01-11T18:28:07.459+01:00| usbCCIDEnumCards| I120: USB-CCID: Card enum thread exiting.
2013-01-11T18:28:07.460+01:00| vmx| I120: scsi0:0: numIOs = 4353 numMergedIOs = 6 numSplitIOs = 4 (40.0%)
2013-01-11T18:28:07.460+01:00| vmx| I120: Closing disk scsi0:0
2013-01-11T18:28:07.906+01:00| vmx| I120: AIOWIN32C: asyncOps=4077 syncOps=248 bufSize=0Kb fixedOps=0 sgOps=4271 sgOn=1
2013-01-11T18:28:07.906+01:00| aioCompletion| I120: AIO thread processed 4077 completions
### Everything works swiftly until now, look the timestampe between these two records (1' 19" delay)
### during this delay vmware player remains black, it seems waiting something to happen
### when the situation unlocks I got these errors and shutdown proceed quickly
2013-01-11T18:29:26.064+01:00| vmx| I120: WORKER: asyncOps=2 maxActiveOps=1 maxPending=0 maxCompleted=1
2013-01-11T18:29:26.065+01:00| vmx| I120: Policy_SavePolicyFile: invalid arguments to function.
2013-01-11T18:29:26.065+01:00| vmx| I120: PolicyVMX_Exit: Could not write out policies: 15.
2013-01-11T18:29:26.065+01:00| WinNotifyThread| I120: WinNotify thread exiting
2013-01-11T18:29:26.171+01:00| vmx| I120: Vix: [6576 mainDispatch.c:3854]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2013-01-11T18:29:26.171+01:00| vmx| I120: Vix: [6576 mainDispatch.c:3873]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.
2013-01-11T18:29:26.196+01:00| vmx| I120: Vix: [6576 mainDispatch.c:3854]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
2013-01-11T18:29:26.196+01:00| vmx| I120: Vix: [6576 mainDispatch.c:3873]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.
2013-01-11T18:29:26.196+01:00| vmx| I120: Transitioned vmx/execState/val to poweredOff
2013-01-11T18:29:26.196+01:00| vmx| I120: VMX idle exit
2013-01-11T18:29:26.196+01:00| vmx| I120: VMIOP: Exit
2013-01-11T18:29:26.199+01:00| vmx| I120: Vix: [6576 mainDispatch.c:859]: VMAutomation_LateShutdown()
2013-01-11T18:29:26.199+01:00| vmx| I120: Vix: [6576 mainDispatch.c:809]: VMAutomationCloseListenerSocket. Closing listener socket.
2013-01-11T18:29:26.200+01:00| vmx| I120: Flushing VMX VMDB connections
2013-01-11T18:29:26.200+01:00| vmx| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
2013-01-11T18:29:26.200+01:00| vmx| I120: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)
2013-01-11T18:29:26.204+01:00| vmx| I120: VMX exit (0).
2013-01-11T18:29:26.204+01:00| vmx| I120: AIOMGR-S : stat o=2 r=12 w=0 i=0 br=111616 bw=0
2013-01-11T18:29:26.204+01:00| vmx| I120: OBJLIB-LIB : ObjLib cleanup done.
2013-01-11T18:29:26.204+01:00| vmx| I120: FileTrack_Exit: done

 

 

I noticed the same problem on any other vm, with different guests os (linux and Windows) with the latest vmware tools installed.

 

Do you have any suggestions?

 

Thanks for help


Viewing all articles
Browse latest Browse all 5660

Trending Articles