Enviroment shuts down. powerDown() in log file

[CEdw2014]

Hi all

I am a VirtualBox newbie and I am having problems with my VirtualBox environment shutting down intermittently. I will be using it for a few hours OK and for no reason it starts to shut down. I have looked at the log file and have noticed the following entries:

01:04:07.134709 ***
01:04:07.135158 ***
01:04:07.135161 ************** End of Guest state at power off ***************
01:04:07.309127 PDMR3PowerOff: 173 414 340 ns run time
01:04:07.309193 Changing the VM state from 'POWERING_OFF' to 'OFF'.
01:04:07.836768 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
01:53:39.305566 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000f010000 w=1600 h=806 bpp=32 cbLine=0x1900, flags=0x3
01:53:39.323816 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000f010000 w=1600 h=806 bpp=32 cbLine=0x1900, flags=0x3

Can I setup the VirtualBox so it never powers off automatically.

I hope you can help>
Colin

[socratis]

Please read the following: Minimum information needed for assistance. Post the VBox.log as a compressed attachment.

[CEdw2014]

1) The VirtualBox I am using is 4.3.6.r91406 and I have installed the Guest Additions.
2) The Host is a Windows 7 and the Guest is a Windows Server 2012 Standard. Both are 64bit. The Host has 8GB Ram and the Guest has 6GB Ram. Please note this configuration works perfectly within VMware Workstation without crashing or shutting down.
3) Logs attached

[Perryg]

Was the guest originally created with vmware, and was it configured to use split files?

[CEdw2014]

Yes to both of your questions.

The machine was originally created using VMWare Workstation and configured with split files.

[Perryg]

While VirtualBox will handle vmdk as far as a format goes it may not handle a guest created with a different program as well as it would its own format.
Same thing with trying to use a VirtualBox created guest in vmware. It just is not the same. If you read the log files you can see what I mean. There are places where VirtualBox is struggling with running the guest. Specifically after you read the splits.

Now having said that you might want to down grade VirtualBox to 4.2.20 to make sure that the new 4.3.* is not producing a regression. They changed the properties a lot in 4.3 and are still trying to clean up the code. If you do down grade be sure to remove the 4.3.6 guest additions first and then install the 4.2.20 guest additions when you have it running again.

One last thing just to clear up the original question. VirtualBox is not powering the guest down. The guest is.

[CEdw2014]

I recreated the Windows Server environment using VirtualBox and everything is working OK, Thanks Perryg