VirtualBox

Ticket #12802 (closed defect: invalid)

Opened 4 years ago

Last modified 16 months ago

Block of loading procedure for Mavericks installation on new MacBook Pro

Reported by: Il Fenomeno Owned by:
Priority: major 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

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

Change History

comment:1 Changed 4 years ago by frank

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

Changed 4 years ago by Il Fenomeno

VBox.log

Changed 4 years ago by Il Fenomeno

Snapshot of blocked screen

comment:2 Changed 4 years ago by Il Fenomeno

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 Changed 4 years ago by frank

Any change with VBox 4.3.10?

comment:4 Changed 4 years ago by MarcinS

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.

Changed 4 years ago by MarcinS

comment:5 Changed 4 years ago by Kamu

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.

Version 0, edited 4 years ago by Kamu (next)

comment:6 Changed 4 years ago by dsmccombs

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 Changed 4 years ago by wolfish17

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 Changed 4 years ago by dsmccombs

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 Changed 4 years ago by wolfish17

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

comment:10 follow-up: ↓ 11 Changed 4 years ago by 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. :(

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

comment:11 in reply to: ↑ 10 Changed 3 years ago by sanyal

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 Changed 3 years ago by jozie

just to say the same issue reappears 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 quoted above do the trick - thanks a lot guys!

log now shows

Gst: 00000001  000206a7 00020800 80180201 178bfbff
Hst:           00040651 01100800 7ffafbff bfebfbff
Last edited 3 years ago by jozie (previous) (diff)

comment:13 Changed 3 years ago by serge84

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 Changed 16 months ago by socratis

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 Changed 16 months ago by vushakov

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

www.oracle.com
ContactPrivacy policyTerms of Use