VirtualBox

Opened 10 years ago

Closed 9 years ago

#13951 closed defect (fixed)

OSX 10.10.2 Kernel Panic on Early 2015 Macbook Pro

Reported by: caleblloyd Owned by:
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 (2)

vbox-panic.txt (8.2 KB ) - added by caleblloyd 10 years ago.
Kernel Panic Output
vbox-panic-4.3.26.txt (8.2 KB ) - added by James Wheare 9 years ago.
Panic trace on 4.3.26

Download all attachments as: .zip

Change History (10)

by caleblloyd, 10 years ago

Attachment: vbox-panic.txt added

Kernel Panic Output

comment:1 by caleblloyd, 10 years ago

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

comment:2 by ohseemedia, 10 years ago

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 10 years ago by ohseemedia (previous) (diff)

comment:3 by Frank Mehnert, 10 years ago

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

comment:4 by Frank Mehnert, 10 years ago

Resolution: fixed
Status: newclosed

Fix is part of VBox 4.3.26.

by James Wheare, 9 years ago

Attachment: vbox-panic-4.3.26.txt added

Panic trace on 4.3.26

comment:5 by James Wheare, 9 years ago

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 by James Wheare, 9 years ago

Resolution: fixed
Status: closedreopened

comment:7 by Frank Mehnert, 9 years ago

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 by Frank Mehnert, 9 years ago

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette