VirtualBox

Opened 11 years ago

Closed 11 years ago

#11287 closed defect (worksforme)

OSX 10.8 - Your computer was restarted because of a problem

Reported by: diggabyte Owned by:
Component: other Version: VirtualBox 4.2.4
Keywords: driver kext osx crash Cc:
Guest type: Linux Host type: Mac OS X

Description

VirtualBox continually causes my brand new OS X 10.8 MacbookPro crash with a grey screen of death that says 'Your computer was restarted because of a problem'. This does not ever occur when virtual box is not running. A VM need not even be running, but just the VirtualBox app seems to cause this crash. This happened in the last major version as well, as the recent update has not fixed the issue.

I've attached both the VBox log and the OS X Crash Report.

Attachments (2)

vbox.log (69.8 KB ) - added by diggabyte 11 years ago.
VBox Log
osx_crash_report.txt (8.4 KB ) - added by diggabyte 11 years ago.
OS X Crash Report

Download all attachments as: .zip

Change History (7)

by diggabyte, 11 years ago

Attachment: vbox.log added

VBox Log

by diggabyte, 11 years ago

Attachment: osx_crash_report.txt added

OS X Crash Report

comment:1 by Frank Mehnert, 11 years ago

Can you provide any steps how to reproduce this crash? If I understand you correct then you host crashes only occasionally, right?

comment:2 by diggabyte, 11 years ago

Steps:

  1. Run virtual box and guest (running bridged network adapter)
  2. Put the host machine to sleep (close lid of Macbook)
  3. Leave it in sleep mode for a while (typically overnight)
  4. Awaken the host machine

Expected: The machine resumes where it left off

Actual: Grey screen of death, org.virtualbox.kext.VBoxNetAdp is always the most recently loaded kext indicated in the crash report.

comment:3 by diggabyte, 11 years ago

It could also be related to switching from one host network interface from another. For example, I use ethernet at work, but at home I use wifi. Perhaps changing between these two causes a crash in the VBoxNetAdp? In other words, use ethernet, sleep the host, awake without ethernet present but with wifi present.

comment:4 by vasily Levchenko, 11 years ago

Could you please before "puting the host to sleep" collect state of your host state with sysdiagnose -f <some place except /tmp/> and on finish put host to sleep. After crash attach archieve with logs + crash report and VBox.log from the session.

Version 0, edited 11 years ago by vasily Levchenko (next)

comment:5 by Frank Mehnert, 11 years ago

Resolution: worksforme
Status: newclosed

No response, closing.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use