Page 1 of 1

[Solved] Install of VB 5.2.22 on MacOS 10.14.2, Fails at Install, No Error Msg Nbr

Posted: 12. Dec 2018, 17:33
by JPQuinn
Hello, I am on a MacbookPro (MacOS Mojave v 10.14.2), and installed the Virtual Box for Mac V 5.2.22, and during the last step of install, I get a simple message saying the install failed, no error number, nothing. I have uninstalled and reinstalled, as well and redownloaded the .dmg, and it's the same story.

But it did install something, I then successfully downloaded and imported EndPointProtector Virtual appliance v 5.1.0.2 (both .OVF and .OVA). Pretty straight forward. When I go to Start, and I get these errors, any ideas on what I should try, would love to use VB on the Mac.

Also, I have Parallels 14 Pro Edition, have loads of VM's and appliances there, and d/l'd the .PVM file, and tried to use that appliance in Parallels on the Mac, and when going to Start the EndPointProtector VM/Appliance, it begins to boot up, and then freezes and goes no further:

(errors from VirtualBox)
Kernel driver not installed (rc=-1908)
Make sure the kernel module has been loaded successfully.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
Failed to open a session for the virtual machine Endpoint Protector 5.1.0.2. Virtual Appliance_1.The virtual machine 'Endpoint Protector 5.1.0.2. Virtual Appliance_1' has terminated unexpectedly during startup with exit code 1 (0x1).Result Code: NS_ERROR_FAILURE (0x80004005)Component: MachineWrapInterface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Many thanks for help, and please let me know what additional details I can share.

Re: Install of VB 5.2.22 on MacOS 10.14.2, Fails at Install, No Error Msg Nbr

Posted: 12. Dec 2018, 18:09
by socratis
JPQuinn wrote:Kernel driver not installed (rc=-1908)
If you had just searched for that phrase in the forums, it would have landed you here, a sticky in the "OSX Hosts" area: Installation fails on 10.13.x, 10.14.x (rc=-1908).

Read it (first post, the red part) and take appropriate action...

Re: Install of VB 5.2.22 on MacOS 10.14.2, Fails at Install, No Error Msg Nbr

Posted: 12. Dec 2018, 19:55
by JPQuinn
thank you, I stepped through that procedure, and it now still starts, but freezes at the appliance booting up step: Starting NGINX, etc... everything eas starting/stopping fine then it freezes. For the first time I ran it, it requested I go give access for the app to have control, which I did through system preferences. So now VB freezes at the same exact point in the same way, as does Parallels running the same appliance.

Re: Install of VB 5.2.22 on MacOS 10.14.2, Fails at Install, No Error Msg Nbr

Posted: 12. Dec 2018, 20:28
by socratis
JPQuinn wrote:thank you, I stepped through that procedure, and it now still starts
OK, you should stop right there! ;)
The title and the problem of this thread has to do with VirtualBox installing. That has been Solved and I'll mark the thread as such. If you have a problem with a specific VM, that's another issue. And since we try to observe the 1 thread per issue, 1 issue per thread, can you open a new thread with an appropriate title?

I'm telling you from now that we're going to need details about the VM that you're trying to run, including a link (if available), so that we can download and test the VM (if possible), and a complete VBox.log. Here's the procedure for getting the log:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
But, do that in a new thread. I'm going to close this as [Solved].

Re: [Solved] Install of VB 5.2.22 on MacOS 10.14.2, Fails at Install, No Error Msg Nbr

Posted: 12. Dec 2018, 22:35
by JPQuinn
Thank you very much. I'll start a new thread with the newly created log file hopefully capturing the error.