4.2.1 Fails to install on IvyBridge Mt. Lion

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
gboswellsac
Posts: 16
Joined: 8. Sep 2008, 06:11

4.2.1 Fails to install on IvyBridge Mt. Lion

Post by gboswellsac »

First Kudo's to Oracle/VirtualBox for the responses and fixes for Mt Lion and Apple IvyBridge issues. I have the infamous Mid 2012 IvyBridge 13" MBP and had to upgrade to 10.8.2 to be able to use the projectors in the classroom (recommendation from MacRumors after Apple Support said live with the shutting down and reboot every time connecting to VGA projector using Apple's thunderbolt to VGA connector) . Now with 10.8.2 VirtualBox will not start with 4.1.23 (see below) and installing 4.2.1 fails to install . VB 4.1.23-80 will install but gives this error when trying to start virtual ( Virtual worked with Lion on pre-ivy bridge , I believe I have in notes it did work on ivyBridge with Lion as it did work for my students with Lion IvyBridge):

> Failed to open a session for the virtual machine Fedora 13 TEST.
>The virtual machine 'Fedora 13 TEST' has terminated unexpectedly during startup with exit code 1.
>Result Code: NS_ERROR_FAILURE (0x80004005)
>Component: Machine
>Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

Also separate error shows up as :
>RTR3init failed with rc=-1912 (rc=-1912)

I removed the 4.1.23-80 and tried to install the 4.2.1-80871 and get the Installation Failed to Install contact the Manuf.....

Sorry to be asking for assistance but I have two students with the same problem and I need to find a solution. Will attempt anything you might suggest. Thanks for any assistance. These surfaced only after the 10.8.2 upgrade from 10.7.2. BTW I was told to start a new thread in the old thread, hope this is ok.

Thanks
gboswellsac
Posts: 16
Joined: 8. Sep 2008, 06:11

Re: 4.2.1 Fails to install on IvyBridge Mt. Lion

Post by gboswellsac »

I just downloaded and reinstalled 4.2.1 latest and the extension pak ..... everything worked even my Windows 3.1 virtual. Thank you for the fix. It feels great to have everything working again. You guys/gals at VirtualBox are great. :oops:
Post Reply