VirtualBox

Ticket #13951 (closed defect: fixed)

Opened 3 years ago

Last modified 23 months ago

OSX 10.10.2 Kernel Panic on Early 2015 Macbook Pro

Reported by: caleblloyd Owned by:
Priority: major Component: other
Version: VirtualBox 4.3.24 Keywords:
Cc: Guest type: Linux
Host type: Mac OS X

Description

Using the new Early 2015 Macbook Pro (MacBookPro12,1), trying to start boot2docker vm using  https://github.com/boot2docker/osx-installer

The VM will initialize fine in VirtualBox, however when starting either from vbox-headless or the VirtualBox UI, I get a kernel panic.

Tested in 4.3.24 and 4.3.22, kernel panic in same places in both. Kernel panic output attached, happy to provide more logs if you tell me how.

Attachments

vbox-panic.txt Download (8.2 KB) - added by caleblloyd 3 years ago.
Kernel Panic Output
vbox-panic-4.3.26.txt Download (8.2 KB) - added by jwheare 2 years ago.
Panic trace on 4.3.26

Change History

Changed 3 years ago by caleblloyd

Kernel Panic Output

comment:1 Changed 3 years ago by caleblloyd

Just tested with test build in 4.3.25 and this has been fixed, can be closed.

comment:2 Changed 3 years ago by ohseemedia

Just wanted to add that I experienced the same issue on a new Early 2015 13" rMBP running VirtualBox through Vagrant + Homestead on version 4.3.24 and 4.3.22. Running the latest test build (4.3.25) also fixed the issue for me.

Last edited 3 years ago by ohseemedia (previous) (diff)

comment:3 Changed 3 years ago by frank

Thanks for the feedback! We will release a maintenance update soon.

comment:4 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Fix is part of VBox 4.3.26.

Changed 2 years ago by jwheare

Panic trace on 4.3.26

comment:5 Changed 2 years ago by jwheare

I'm still experiencing this issue from time to time on 4.3.26 when launching a VM. I've attached the panic report.

comment:6 Changed 2 years ago by jwheare

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:7 Changed 2 years ago by frank

This was properly fixed in VBox 5.0. VBox 5.0.4 should work fine on your host. If you insist on running VBox 4.3.x, please try the latest 4.3.x test build from here, it should contain the necessary fixes as well.

comment:8 Changed 23 months ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use