VMWare workstation automatically shutting down after 45min

[gvraman81]

Hi,

I have a VM (VMWare workstation) with Windows 2008 R2 (.net and Sharepoint configured) is getting auto shutdown after around 45 min. Kindly help required to fix this issue.

Note: My VMware workstation is licensed one.

Regards,

Venkat.

[mfelker]

Porbably need more information (host oprerating system and hardware).  It would be futile to speculate unless these were posted.

[WoodyZ]

I have a VM (VMWare workstation) with Windows 2008 R2 (.net and Sharepoint configured) is getting auto shutdown after around 45 min. Kindly help required to fix this issue.

Just to be clear, is it just the Windows 2008 R2 Virtual Machine that is preforming an "auto shutdown after around 45 min" or is it the Host system?  I'm assuming it's just the Windows 2008 R2 Virtual Machine however being explicit and specific is always a better approach when expressing issues when asking for help.  Additionally on the assumption that it's the Windows 2008 R2 Virtual Machine not the Host is this the only Virtual Machine you're having this particular type of issue with?  In addition to the answers to these questions what version/build of VMware Workstation are you using and what OS is installed on the Host?

Other information that might be helpful if to archive (compress) and attach in a single .zip file the vmware*.log files for the target Virtual Machine, especially so directly after an auto shutdown occurrence.

[a_p_]

Welcome to the Community,

please check whether the guest OS "Windows 2008 R2" has been activated.

André

[mfelker]

WooyZ.  Since you have brought up the time stamps of replies before  please note that your  response was the same as my request for information at least in so far as the host specs are concerned - howeve rit was 16 minutes later .

That aside if the Windows Server 2008 R2 guest  shuts  down without reason there should be a dialog about the reason why when you restart this VM.  Server VM's always produce such dialogs in my expernece at least. You have t oenter at   least  some character in order to ontinue (mosty  I just enter "x".)  Have you run chkdsk on the guest?  You most likely have some lost  clusters and perhaps other file system eroors. 

[gvraman81]

my host operating system was windows 7 home premium .

Hardware: Dell I7 Laptop, 8GB Memory.

[a_p_]

The host OS usually isn't involved if a VM/guest shuts down. So again the question, did you already activate your Windows server guest. Without activation - after the grace period has expired - Windows automatically shuts down after a certain amount of time.

André

[gvraman81]

Hi,

Thanks for your reply.

How to check whether my guest windows got activated?

[a_p_]

Open "Control" -> "System" or right click "Computer" and select "Settings". At the bottom of the Window that opens you will see the activation status.

André

[gvraman81]

Please see the attached screen with windows activation.

[WoodyZ]

I'm just curious, is there any particular good reason why you've not answered the questions I've asked in Re: VMWare workstation automatically shutting down after 45min or provided the vmware.log file as requested after a shutdown incident?

[mfelker]

At least we know from the screenshot he is referring to a guest and not the host!

You can find the vmware.log(s) in C:\Users\<your user name>\\My Documents\Virtual Machines\Server 2008 \(this is a directory!)  You could also go t oHelp and produce support files and send those.

[gvraman81]

sorry for delayed response.i was not feeling well.

attached the log files

[mfelker]

I looked at the log and actually saw where  WS waS shutdown. Here the lines

0| UHCI: HCReset
Dec 05 22:00:31.255: vcpu-0| SCSI0: RESET BUS
Dec 05 22:00:31.857: vcpu-0| PIIX4: PM Soft Off.  Good-bye.
Dec 05 22:00:31.874: vmx| Stopping VCPU threads...
Dec 05 22:00:31.901: mks| Ending MKSRole pseudocalls, state was 1
Dec 05 22:00:31.901: mks| Detaching from window system.
Dec 05 22:00:31.906: mks| MKS: Base polling period is 1000000us

Just  before this:

TOOLS unity.show.taskbar failed: failure of the transport layer
Dec 05 21:59:46.255: vcpu-0| GuestRpc: Channel 3 reinitialized.
Dec 05 21:59:46.255: vcpu-0| GuestRpc: Channel 3 reinitialized.
Dec 05 21:59:46.255: vcpu-0| GuestRpc: Channel 3 reinitialized.
Dec 05 21:59:46.638: vmx| GuestRpcSendTimedOut: message to toolbox timed out.
Dec 05 21:59:46.638: vmx| GuestRpc: app toolbox's second ping timeout; assuming app is down
Dec 05 21:59:52.123: mks| MKS switching absolute mouse off
Dec 05 22:00:31.221: vcpu-0| UHCI: HCReset
Dec 05 22:00:31.255: vcpu-0| SCSI0: RESET BUS
Dec 05 22:00:31.857: vcpu-0| PIIX4: PM Soft Off.  Good-bye.
Dec 05 22:00:31.874: vmx| Stopping VCPU threads...
Dec 05 22:00:31.901: mks| Ending MKSRole pseudocalls, state was 1
Dec 05 22:00:31.901: mks| Detaching from window system.
Dec 05 22:00:31.906: mks| MKS: Base polling period is 1000000us
Dec 05 22:00:31.906: mks| Async MKS thread is exiting
Dec 05 22:00:31.907: vmx| Vix: [6972 mainDispatch.c:1015]: VMAutomation_PowerOff: Powering off.
Dec 05 22:00:31.938: vmx| TOOLS received request in VMX to set option 'enableDnD' -> '0'
Dec 05 22:00:31.938: vmx| TOOLS received request in VMX to set option 'copypaste' -> '0'
Dec 05 22:00:31.938: vmx| TOOLS received request in VMX to set option 'copypaste' -> '0'
Dec 05 22:00:32.004: vmx| VMXVmdb_SetToolsVersionState: status value set to 'ok'
Dec 05 22:00:32.015: vmx| USB: Disconnecting device 0x200000010e0f0002
Dec 05 22:00:32.016: vmx| USB: Disconnecting device 0x400000010e0f0003
Dec 05 22:00:32.079: vmx| MKS local poweroff
Dec 05 22:00:32.101: usbCCIDEnumCards| USB-CCID: Card enum thread exiting.
Dec 05 22:00:32.156: vmx| scsi0:0: numIOs = 34249 numMergedIOs = 3016 numSplitIOs = 140 ( 4.4%)
Dec 05 22:00:32.994: vmx| AIOWIN32C: asyncOps=37641 syncOps=248 bufSize=372Kb fixedOps=622 sgOps=32964 sgOn=1

I will lhave eave the complete analysis of the log to somebody else however it seems to me that you  could try to uninstall VMware Tools and see if that makes a difference.  Mainly it looks like a problem with your internal netwwork.

The log itself is not  extremely long so  perhaps somebody with mroe knowledge  of  the vmware.log could look at  this.

Good luck!!

[dariusd]

The vmware.log shows that something inside the guest OS is requesting a shutdown of the VM.  Specifically, "PIIX4: PM Soft Off.  Good-bye." always indicates that the guest OS has powered itself off... VMware Workstation is only shutting down the VM because the OS (or something running in the OS) asked it to.

Check in the guest's Event Viewer to see if there's any reason given for the shutdown.

Cheers,

--

Darius

[gvraman81]

Hi,

I have quick question. My Dell XPS Laptop has 8 GB Ram, Windows 7, Home Premium (64Bit)., and I have allocated 6GB for Guest OS (VM) that's the cause for  this problem?

Regards

Venkat.

[dariusd]

Hi Venkat,

It's unlikely that allocating 6 GBytes of RAM to the VM would directly cause the problem, unless there is some software inside the VM that doesn't like having 6 GBytes available and decides to shut down the VM as a result.

Please check the event logs inside the guest (Start > Run, then type eventvwr and press Enter) and report what you see there in the System logs at the time the VM shuts down.

Thanks,

--

Darius

[mfelker]

  The  term "Good bye" does not nessceraly imply an  error situation  but instead a  satifactory ending.  This  is   true for    example in  a succeful shutdown the process   was truly messed up you   would expect a blue screen message - which in  fact   has happened but not in  your case.  The VMwafe procesw(es) tried to connect to the host  for 45 minutes - pretty  persistent.  This is the  way I   read the log anyway - but let othrd   decide for you   or you   yourself may choose to interpret and act  on it.  So again  I say

Good luck