Now, after a successful upgrade, when I try to start Virtual Box, I get the following message: Would it help if I go back to Virtual Box v3.2.8? There are a variety of options you can try for this: I upgraded Virtual Box [again] to v4.0.4 and copied the three dll files from the "For VBox4.0.0" directory to the Virutal Box install directory rather than the system32/drivers directory. Is there any particular reason for the suggestion to copy them to the drivers directory instead? BTW, I tried both Virtual Box 4.1.20 and 4.1.22 (with the dlls "For VBox4.1.2") and both versions Other versions of Virtual Box may work but they aren't supported.
I did this because the old dll files had been copied there. The relase notes for the latest versions of SP states that the latest supported version of Virtual Box is v4.1.12 ( That seems to indicate that the latest supported version is 4.1.2. So if you try and use those versions and need assitance then you will need to change to a supported version before receiving help.
Looks like this is a package based installation, which is common for Ubuntu Cloud Image.
IT pros use Workstation products to securely connect with v Sphere, ESXi or other Workstation servers to manage virtual machines and physical hosts.
A common hypervisor platform maximizes agility and productivity by enabling easy transfer of virtual machines to and from your local PC.
I'm trying to upgrade the guest box additions of a Ubuntu Precise box from 4.2 to 4.3 after upgrading Virtualbox (4.3.0) and Vagrant (1.3.5).
The plugin correctly detects a version mismatch, installs dependencies and kicks of the installer.