VirtualBox

Opened 10 years ago

Closed 8 years ago

#12802 closed defect (invalid)

Block of loading procedure for Mavericks installation on new MacBook Pro

Reported by: Il Fenomeno Owned by:
Component: host support Version: VirtualBox 4.3.8
Keywords: osx, mavericks, macbook pro, 2013 Cc:
Guest type: OSX Server Host type: Mac OS X

Description

Hardware: Apple MacBook Pro 13', retina, end of 2013 Host: OSX Mavericks 10.9.2 Guest: OSX Maverick 10.9.2 VirtualBox 4.3.8

After create and leave the configuration as default on the virtual machine, I'm booting from the disc image of Mavericks.

With this settings the VM start but nothing it is visibile on it so it not possible to understand if the system is loading. Changing the chipset settings to PIIX3, now the content is visible, but the loading procedure stops after the step:"hfs: mounted OS X Base System on device root_device".

Applying the same procedure on a MacBook Pro, 15', half 2010 Host: OSX Mavericks 10.9.2 Guest: OSX Maverick 10.9.2 VirtualBox 4.3.8

After create and leave the configuration as default on the virtual machine, I'm booting from the disc image of Mavericks. Everything works fine. Exporting that machine to the previous described Mac, the issue is the same.

Attachments (3)

VBox.log (67.2 KB ) - added by Il Fenomeno 10 years ago.
VBox.log
Blocked screen.png (221.3 KB ) - added by Il Fenomeno 10 years ago.
Snapshot of blocked screen
VBox-MarcinS-Haswell-Mavericks.log (71.6 KB ) - added by MarcinS 10 years ago.

Download all attachments as: .zip

Change History (18)

comment:1 by Frank Mehnert, 10 years ago

I miss the VBox.log files for your failed sessions.

by Il Fenomeno, 10 years ago

Attachment: VBox.log added

VBox.log

by Il Fenomeno, 10 years ago

Attachment: Blocked screen.png added

Snapshot of blocked screen

comment:2 by Il Fenomeno, 10 years ago

As requested, I have put in attach the VBox.log file. There is also a screenshot on the point on which the loading procedure is hung

comment:3 by Frank Mehnert, 10 years ago

Any change with VBox 4.3.10?

comment:4 by MarcinS, 10 years ago

I'm seeing this same issue, with 4.3.10 as well - boot hangs just after HFS mount.

Apparently this is specific to the new Haswell Macbook Pros, this page mentions that "All Macs using Intel Haswell CPU (Macs after 2013) currently have an unknown issue prevents booting. I tested mach_kernel compiled without XCPM (XNU CPU Power Management), but it still doesn't work.":

http://ntk.me/2012/09/07/os-x-on-os-x/

This was the first matching issue I was able to find raised against VirtualBox. I've attached my VBox.log in case it provides something different than the original submitters.

by MarcinS, 10 years ago

comment:5 by Kamu, 10 years ago

I am hanging at the same point, but I'm on Windows 7, running latest 4.3.10. I am running a new Intel Core i7 4771. Trying to install Mavericks 10.9.2.

Last edited 10 years ago by Kamu (previous) (diff)

comment:6 by dsmccombs, 10 years ago

Seeing the same problem on 4.3.10 on a Ubuntu 14.04 64-bit host running on a Haswell processor. I haven't seen any work arounds in either Virtualbox or in the VM itself to get this working yet.

comment:7 by wolfish17, 10 years ago

I have the same problem with similar hardware to the original post. What I would like to add is that the CPU was cranking away intensely on the virtualbox process of the stalled Mavericks boot (same screen as image "Blocked screen.png" posted above) until I terminated it via the virtualbox menu. I waited about one hour until I concluded it wasn't doing anything productive.

comment:8 by dsmccombs, 10 years ago

I've found that you can work around this by setting the CPUID to an older processor. I think OS X is trying to use some Haswell feature that isn't exposed via virtualization.

VBoxManage modifyvm <vmname> --cpuidset 00000001 000306a9 00020800 80000201 178bfbff

The above sets the CPU to look like an Ivy Bridge.

comment:9 by wolfish17, 10 years ago

The --cpuidset suggested above worked for me. Thank you for posting it.

comment:10 by Xu Xin, 10 years ago

This work around makes the vm very very slow on a Macbook Pro Late 2013 13" i5 Haswell. Is there another cpu id that will make it work faster? Please help I really need this. Thanks.

PS: and the VRAM inside the VBox is only 3MB despite the fact that i've setted up to 128MB. :(

Last edited 10 years ago by Xu Xin (previous) (diff)

in reply to:  10 comment:11 by sanyal, 10 years ago

Replying to Xu Xin:

This work around makes the vm very very slow on a Macbook Pro Late 2013 13" i5 Haswell. Is there another cpu id that will make it work faster? Please help I really need this. Thanks.

PS: and the VRAM inside the VBox is only 3MB despite the fact that i've setted up to 128MB. :(

I saw a similar issue with my Mountain Lion vm. It was running very very slow on my MacBook Air Mid 2013 13" i5 Haswell. I tried this and it is now fast enough for me

VBoxManage modifyvm <vmname> --cpuidset 1 000206a7 02100800 1fbae3bf bfebfbff

comment:12 by jozie, 10 years ago

I am seeing the same issue with virtualbox 4.3.12 as well (hangs on the HFS mount line)

host Mavericks 10.9.2, guest Mavericks 10.9.2 on mid-2013 MBA with Haswell i7-4650U

both --cpuidset lines do the trick. But feels a bit slow.

log now shows

Gst: 00000001  000206a7 00020800 80180201 178bfbff
Hst:           00040651 01100800 7ffafbff bfebfbff
Version 0, edited 10 years ago by jozie (next)

comment:13 by serge84, 9 years ago

I try to setup Mavericks, Lion and Mountain Lion on Mac Mini 2014 and it didn't work on virtualBox 4.3.18. Could you please provide any help.

comment:14 by Socratis, 8 years ago

Please someone close this. It's not obsolete, it's not invalid, it's not won'tfix. It's all the above and more. Bogus claims that don't make sense. If you could send it to oblivion, the better! Half of the posts are Hackintosh and the rest are pure... magic! And it's being used as a reference of a working setup!

comment:15 by Valery Ushakov, 8 years ago

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use