Updating older versions of sun virtualbox
It returned 1 pkg to be removed (5.1) and one to be installed (5.2).I let it do its thing and the install came out fine.
Building the Virtual Box kernel modules Virtual Box has been installed successfully.With the Guest Additions in the (pseduo) CD drive I was able to install the Guest additions.This ended requiring a reboot of the guest machine. Warning about breaking 5.1.18 installation suggests that I must completely remove the old version before installing the new version plus its extensions. Yes, upgrading VB to another major version (where in x.y.z x or y are different), makes an uninstall of the old version necessary. As soon as you launch the BN manager for the new version the first time you will get a prompt to update it.Presently, Virtual Box runs on Windows, Linux and Mac hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, Windows 7, Windows 8, Windows 10), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x and 4.x), More...Presently, Virtual Box runs on Windows, Linux and Mac hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, Windows 7, Windows 8, Windows 10), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x and 4.x), Solaris and Open Solaris, OS/2, and Open BSD.Please notify me if you find any typo/grammar/language mistakes.
Oracle Virtual Box is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use.
Forum rules There are no such things as "stupid" questions.
However if you think your question is a bit stupid, then this is the right place for you to post it.
Before you post please read how to get help apparently, to upgrade to Virtualbox 5.1 we need to do a remove and re-install,-- So,,-- can I do it this way: 1.
make sure i have the 5.1 package in downloads/vbox51 from Oracle; 2.
so that link was followed, as always, and the v5.1 was obtained. all was sweet & everything was still in-place: ie: I'd not removed any existing VBs & they were still in-place & they still worked But you should have quitted all existing VMs before upgrading - that means not closed them to a saved state; in this case there is a chance, that you cannot reopen them without discarding the saved state at running my VB v5.0.x one day, it gave the usual notice about some upgrade being available, but, this time, it was for v5.1 instead of the usual v5.0.x as it always was.