upgrade to Yosemite seems to have killed VM

[mosseyuk]

Hi,
I am user of VM on an iMac with Windows 7 as the guest OS. I upgraded to OS X Yosemite this morning and now when I try to start a session I get the following :
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {22781af3-1c96-4126-9edf-67a020e0e858}

and no virtual machine . I use this for work so need help as swiftly as possible. If anyone has any ideas please let me know. I wondered wether it just needed up dating but it says I have the most recent version 4.2.18 r88780 but not sure is this is indeed the case.
ANY help appreciated - Thanks,

[mosseyuk]

also had this alarming note on my desktop from VM

Kernel driver not installed (rc=-1908)

Make sure the kernel module has been loaded successfully.

any suggestions?

[socratis]

First lesson; never, ever upgrade a work machine with a new, untested, unproven operating system. You know that you can try Yosemite from an external hard drive, right?

Second, 4.2.18 is not the latest and greatest. 4.3.18 is and you can find this in the Downloads section of the VirtualBox site.

Third, the message that says the driver is not installed is most probably your main concern. I'm not sure if the kernel drivers for VirtualBox have been tested/working/optimized for Yosemite. Chances are no, because the developers just got their hands on it, but you beat them to the punch. You can only hope that Apple hasn't changed things in an incompatible way to break VirtualBox's functionality.

So, uninstall your old VirtualBox installation (with the 'VirtualBox_uninstall.tool' located in the 4.2.18 .dmg), download the latest and greatest VirtualBox, and if you're religious, start praying...

[loukingjr]

VirtualBox has been working with Yosemite since the first developer previews and the public betas. socratis is most likely correct and you just need a newer version of VirtualBox.

[Joemorelli]

Nope, I am having the same problem as mosseyuk. Installed Yosemite, upgraded to the most recent version of VirtualBox and getting the same error message. Can't install Extensionpack properly because of incompatible Library version: VBoxPuelMain.dylib requires 4.3.18 or later but VBoxVMM.dylib provides version 4.3.16.

[loukingjr]

Correction. It is working for me on two different Macs (see signature). Running VB 4.3.18 on both machines.

[bpn]

Well i just downloaded the latest version and installed it over the existing installation (same version). Voilà ... it's running. Maybe the Yosemite update has overwritten some shit.

[loukingjr]

Well i just downloaded the latest version and installed it over the existing installation (same version). Voilà ... it's running. Maybe the Yosemite update has overwritten some sh**.

I'm not sure but it seems there are a few people having random issues with VirtualBox after they updated to OSX 10.10. I wasn't one of them. Reinstalling VirtualBox does seem to fix most of the issues.

[pictonic]

FWIW my iMac (21.5, mid-2010, 4GB) was running VB 4.3.18 r96516 on Mavericks. I shut down my VB image of Arch linux before I downloaded and installed Yosemite, on the day it was released.
After about 4 hours of grinding away the OS finally rebooted into Yosemite with everything from Mavericks intact, account, apps, ... even down to cached web pages. VB still ran, and runs, normally.
I don't think there is anything inherently wrong with VB on Yosemite, but plenty of room for glitches in that 4 hour upgrade!

[loukingjr]

FWIW my iMac (21.5, mid-2010, 4GB) was running VB 4.3.18 r96516 on Mavericks. I shut down my VB image of Arch linux before I downloaded and installed Yosemite, on the day it was released.
After about 4 hours of grinding away the OS finally rebooted into Yosemite with everything from Mavericks intact, account, apps, ... even down to cached web pages. VB still ran, and runs, normally.
I don't think there is anything inherently wrong with VB on Yosemite, but plenty of room for glitches in that 4 hour upgrade!

4 hours???

VirtualBox runs just fine on 10.10 but installing it did seem to cause some issues for some people. And not just with VirtualBox.