Build & Install the VirtualBox for Yosemite

[wonsange]

Hi, everyone.

I'm using the custom VirtualBox for our system.
So, I build and install our custom VirtualBox (4.3.10).
It runs OK, until Mavericks.

But, for Yosemite, it has one issue.
In the Yosemite, my custom VirtualBox doesn't install and run.
Cause is the kext(kernel extension) authorized.

I found the temporarily solution.
1. Run the [# sudo nvram boot-args="kext-dev-mode=1"], and reboot.
2. Reinstall my custom VirtualBox.

For Yosemite, how can I authorize to .kext files?
I was registered to the Mac Developer.
Please advise for me.

Build Environment
MacOS version: 10.6.8
VirtualBox source version: 4.3.10

[mpack]

What is a "custom VirtualBox"?

VirtualBox is the name of the software. If you are making custom builds of VirtualBox for a host that is supported by official builds, then you're pretty much on your own!

If "custom VirtualBox" just means a VM then I'll want details of the VM: Minimum information needed for assistance.

[loukingjr]

fwiw, VB 4.3.20 runs perfectly well in OSX 10.10.1

[wonsange]

Custom VirtualBox means the VirtualBox builded by me.
I compile and use the VirtualBox Host.
I download the source of the VirtualBox, build the custom virtualbox.

it cannot install at Yosemite caused by un-authorized kext.

Please advise me.

[loukingjr]

OSX build instructions

The bottom line, is if you built VirtualBox from the source code and it ran fine in OSX versions up through OSX 10.9, it will run in OSX 10.10. If there was some difference, there would have to be a separate Yosemite version of VirtualBox but there isn't.

[wonsange]

I was compiled from this site.
I make the dmg file using [kmk packing].
Generated dmg file is working fine until mavericks.
But, Yosemite can not install and run.
Yosemite change the authorized policy.
So, kext files of the compiled VirtualBox cannot install.

How can I authorize?

[Perryg]

I'm afraid that there are so few Mac users that build their own version of VirtualBox you may not get a viable reply. You might try asking someone on the VirtualBox IRC channel as the DEVs monitor that one themselves. https://www.virtualbox.org/wiki/Community

Moving to VirtualBox OSE.

[loukingjr]

Actually I suspect I know what the OP's problem is. Seeing he says his build environment is OSX 10.6.8, his version of XCode is most likely out of date.

I also suspect the authorization policy he is talking about changed with Mavericks and not Yosemite which is in the Mac's Security settings...
Allow apps downloaded from:
Mac App Store
Mac App Store and identified developers
Anywhere

So if his build is viable it should install by choosing "Anywhere".

[loukingjr]

p.s. once you install a program with "Anywhere" enabled it will continue to run, even if you re-enable one of the other two choices. (and you should).

[Perryg]

@Lou,

Color me confused but what does "Allow apps downloaded from" have to do with building your own version of VirtualBox?

Are you saying that to compile your own version still requires the "install" from anywhere, even though you don't actually install it?

[loukingjr]

No, sorry. What I am saying is once you build it you have to change the security settings in order to install it. The OP was getting an authorization error when he was trying to install it.

[loukingjr]

From what I gathered he already had a build he was using which wouldn't install in Yosemite because it was being flagged by the security settings. I suppose he may be trying a new build and wants to circumvent the security settings but I don't know that.

[Perryg]

Alrighty then. I will leave it to the Mac experts.

Although I must say it seems pretty non-productive to "not" allow you to install your own builds without jumping through hoops.

[loukingjr]

LOL you can install your own builds You just have to change the security settings.

You could always leave them set to allow apps from anywhere then you wouldn't have to fuss with them. The settings are there to disallow anyone from downloading or installing bad stuff.

[wonsange]

I found these informations about my error.
http://stackoverflow.com/questions/2667 ... emite10-10
https://github.com/Homebrew/homebrew/issues/31164

After I run the "nvram boot-args=kext-dev-mode=1" and reboot, my virtualbox install successfully.

How can I sign the kext of my VirtualBox?