Page 1 of 1

Crash issues

Posted: 8. Aug 2014, 22:54
by pmang6
Anytime I try to boot a virtual machine it either freezes up and crashes after 30 seconds or fails to start. The host is OS X 10.9.2 on a mid 2010 21.5" iMac. Guest is windows 7. VB version 4.3.14. Guest editions installed. 64bit. Guest memory: 6 gigs. host memory: 6gigs.
I have tried reinstalling.

Log 1:
Can I paste the log here? VB won't save it.



I only have the error report for when it won't open at the moment but I will post the error report for when it crashes while running shortly.

Error report when the VM won't boot.
Failed to open a session for the virtual machine Windows 7.

The VM session was closed before any attempt to power it on.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}

Re: Crash issues

Posted: 8. Aug 2014, 23:34
by loukingjr
you can't set a guest to use the same amount of RAM as your host. Attach your compressed vbox.log file where it says "Upload attachment".

Re: Crash issues

Posted: 8. Aug 2014, 23:39
by pmang6
loukingjr wrote:you can't set a guest to use the same amount of RAM as your host. Attach your compressed vbox.log file where it says "Upload attachment".
I can't get VB to let me save the log, I open the log, click save, the save prompt opens, I name the file and hit save but the file is nowhere to be found.

Re: Crash issues

Posted: 8. Aug 2014, 23:52
by loukingjr
well, first of all the logs are saved automatically in the log folder inside the guest folder inside the VIrtualBox VM folder. However, if you want to save the log manually you have to tell it where you want the log saved to.

you can do a search for vbox.log

Re: Crash issues

Posted: 9. Aug 2014, 02:37
by pmang6
loukingjr wrote:well, first of all the logs are saved automatically in the log folder inside the guest folder inside the VIrtualBox VM folder. However, if you want to save the log manually you have to tell it where you want the log saved to.

you can do a search for vbox.log

Re allotting the ram seemed to do the trick! Thanks!

Re: ***SOLVED. PLEASE LOCK.***

Posted: 9. Aug 2014, 12:22
by socratis
Please change the title of the thread back to its original "Crash issues".

Imagine what would happen if every issue that was resolved had the title "***SOLVED. PLEASE LOCK.***". You couldn't read the forum, because 80% of the threads would have the same title ;)