OS X 10.11 VirtualBox issues

[Guest]

Hello,

 

I'm setting up an OS X 10.11 VM in VirtualBox but I'm having issues with booting it up. I followed this guide for doing it and used the vm image that came with it. I'm using version 5.1.14 r112924 of VirtualBox.

 

When I hit startup, the vm window appears and it seems to work fine, but while still displaying console text, it just stops and doesn't do anything at all, not even any hard drive use in the vm. Here's a screenshot from a bit after it stops:

The line that looks the most important is the 3rd and 2nd last lines, but I am not very familiar with Mac OS so I'll leave the judgement to those that really know what they're doing.

 

How can I solve this problem and get the OS properly working?

 

Thanks for any help.

[knightslugger]

Considering Mac OS X only works on Apple products, this is basically hackintosh talk... which is not allowed for discussion here.

[Guest]

3 minutes ago, knightslugger said:

Considering Mac OS X only works on Apple products, this is basically hackintosh talk... which is not allowed for discussion here.

I'll take it down then, but I'm sure there's a difference between a vm (virtualised operating system running within an other) and a hackintosh (non-apple computer or device running Mac OS as the only OS with no vm or dual boot)... eh.

[corrado33]

5 minutes ago, knightslugger said:

Considering Mac OS X only works on Apple products, this is basically hackintosh talk... which is not allowed for discussion here.

That's not at all true. It's perfectly legal to run OS X in a virtualbox.

 

As for the OP, it looks like a corrupted image or bad install. Did you add the correct code as outlined in the guide?

[lieder1987]

make sure that all of your USB "connected" devices are unplugged and try again. Also it is odd that it is showing all of the text as that is verbose mode and normally something that happens when you are using a bootloader not a standard OSX installation. 

 

In addition to that, make sure that you are virtualizing hardware that have a OSX variant. If you are trying to force it to have "hardware" that doesn't have standard drivers you are not going to be able to boot.

[Master Disaster]

3 minutes ago, corrado33 said:

That's not at all true. It's perfectly legal to run OS X in a virtualbox.

 

As for the OP, it looks like a corrupted image or bad install. Did you add the correct code as outlined in the guide?

Yeah, no. If its using a fake SM BIOS in order to fake Apple registration information then its in breach of Apples TOS.

[Guest]

3 minutes ago, corrado33 said:

That's not at all true. It's perfectly legal to run OS X in a virtualbox.

 

As for the OP, it looks like a corrupted image or bad install. Did you add the correct code as outlined in the guide?

I added the code as instructed, but was a little wary as it said it was for version 5.0.x where I have 5.1.14. Could that be the source of the problem? If not, I'll re-download the image and see if that works, but that was a process that took a whole day with my internet speeds.

 

1 minute ago, lieder1987 said:

make sure that all of your USB "connected" devices are unplugged and try again. Also it is odd that it is showing all of the text as that is verbose mode and normally something that happens when you are using a bootloader not a standard OSX installation. 

 

In addition to that, make sure that you are virtualizing hardware that have a OSX variant. If you are trying to force it to have "hardware" that doesn't have standard drivers you are not going to be able to boot.

I will try this and see what happens.

2 minutes ago, Master Disaster said:

Yeah, no. If its using a fake SM BIOS in order to fake Apple registration information then its in breach of Apples TOS.

I don't know if it is or not, but when it's working I will know.

[Master Disaster]

13 minutes ago, OTheB said:

I don't know if it is or not, but when it's working I will know.

It is, the SM BIOS is a part of the hardware on real Apple equipment that stores the registration information (SN,, manufacture date and location etc) and OS X won't boot without SM BIOS information so your image is using a fake SM BIOS file to pass fake info to the OS at boot.

 

Edit

 

Step 5 of the guide you linked covers setting up the SMC with the SM BIOS info.

[WkdPaul]

Locked, as per the community standards, help into settings up a hackintosh isn't allowed, and as per the Apple ToS it also covers VMs.