virtualbox.org

nearstateandrew wrote:Are you saying that there is a better log I could provide you with, or just that the logs recorded by virtualbox are insufficient?

A bit of both. I asked for "a" log, you provided me with 4 logs and didn't make it clear which - if any - was the important one. However, if VirtualBox is crashing then the log would probably be missing the important last part anyway.

From what you have said so far, I'm under the impression that the VM window just closes without warning and without any error message, is that correct?

I could suggest that you open a BugTracker ticket, but I suspect the devs will be equally unenthusiastic about the lack of good diagnostics - unless you can suggest a way to guarantee that the issue is reproducable.

What I can add is WIndows 8.1 preview randomly aborts as well. My Windows 7 guest will abort randomly if I try and run it full screen as I have mentioned elsewhere. Looking at the logs they always cut off during an OpenGL event.

loukingjr wrote:they always cut off during an OpenGL event.

Drivers issues?

noteirak wrote:

loukingjr wrote:they always cut off during an OpenGL event.

Drivers issues?

I assume so because 3D on Mac hosts has always been iffy. It's much better since 4.2.16. Unity 3D works well as does Cinnamon but Gnome 3 is still a problem.

Yes that is correct. No warning, no anything, the VM just aborts. That is why my question which started this whole discussion was "How to debug Aborting guest". It sounds like the answer is, "there is no way", in which case I just need to find another way to run windows.

For the record, I am reattaching the log file which you and I identified as the one belonging to the abortive session, to clear up any remaining abiguity.