Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Question:

Question: Can't install virtualbox remotely

After over 30 hours of work, I have finally succeeded in upgrading my remote (colocated) Mac OS X 10.10 server to macos High Sierra with server. I had to go from 10.10 to 10.12, update the server data, and then do a fresh install of 10.13 and then import the server (and user and other) data from the 10.12 drive, because the RAID wouldn't work and 10.10 can't upgrade directly to 10.13 and and AND AND AND. Remote installs are a NIGHTMARE.


But it finally works, and is on 10.13. However, what doesn't work now is running VirtualBox. I was told (by a bunch of little popups) when I was moving the data over that virtualbox wouldn't work because the kexts were no longer allowed. So I tried reinstalling it, but it appears that allowing kexts isn't possible remotely. The button just clicks, but nothing happens. I gather this is a security 'feature'; well, fine. I found spctl kext-consent but that doesn't appear to work when booted normally either, even though with root privs I could reformat the entire hard drive or install all sorts of fun spyware.


Is there literally nothing I can do? I depend on virtualbox to run several virtual environments that, you know, are the entire reason I have a remote server in the first place.

Mac mini, macOS High Sierra (10.13.1), macos server, colocated

Posted on

Reply

Page content loaded

Nov 12, 2017 4:10 AM in response to Adam A. Lang In response to Adam A. Lang

I have been tracking virtual box that closely but the last 3 yers of OS X releasees have brought a steady restriction on the accessibility to the hardware. KEXTs are of course Kernel Extensions and exactly where I would expect changes to break hardware access. I would check the virtuabox documentation and see what they are saying about this area of their project development.


It could be that you could turn-off all the extra protection that apple has been adding but I believe that requires physical access to the computer to turn off.


Good Luck,

Ben

Nov 12, 2017 4:10 AM

Reply Helpful

Nov 12, 2017 9:21 AM in response to detourdog In response to detourdog

What do you mean by 'this area of their development'? They have required kexts for a decade, I don't suspect that they are going to stop now.


And yes, even if I wanted to turn off all protection, I believe that has to be done from the recovery partition.

Nov 12, 2017 9:21 AM

Reply Helpful

Nov 12, 2017 9:29 AM in response to Adam A. Lang In response to Adam A. Lang

I meant that the VirtualBox developers are no longer able to expect a default OS X installation to just run KEXTS. The developers have to decide what things truly need Kernel access and then do whatever Apple requires for the KEXTs to just run.


I'm sure the VirtualBox developer mailing list or website describes the issue and what they are doing about it. What they were doing 10 years ago is no longer works in the default environment of signed KEXTs.

If there isn't a lot of talk about this issue over there then I guess is could also just be a bad install of some sort.


That is my guess.


Ben

Nov 12, 2017 9:29 AM

Reply Helpful

Nov 12, 2017 9:31 AM in response to detourdog In response to detourdog

There isn't a lot of discussion about it because all you have to do is be ANY user (not even admin, just anyone) and click a little button that says 'trust this'. The reason I can't do it is because I am logged in remotely over screen sharing.

Nov 12, 2017 9:31 AM

Reply Helpful
User profile for user: Adam A. Lang

Question: Can't install virtualbox remotely