Upgrading from 4.0 to 4.2

[LeeU]

I've checked around the forum and wasn't able to find an answer for this (if there is, please provide the link).

I am running Ubuntu 12.04 with VB 4.0.18 and want to upgrade to VB 4.2.16. Is it possible to just upgrade or do I have to uninstall the previous version and do a clean install with the new version? If so, is there a way to preserve the OS I have installed, as well as the programs?

[mpack]

Nobody can give you guarantees (at least not unless you want to pay?) - making a backup is always a most excellent idea, but you should be able to upgrade directly.

[Perryg]

Linux is kind of strict about major version upgrades needing to have a clean install.

It may work but if it tells you that there is a conflict, just uninstall the older version and install the new one. All guests and control files will remain intact.

But......I always tell everyone to backup as they should be doing anyway if the guests and or data are important to you.

[mpack]

Um. They both have the same major version Perry! (4.x).

[Perryg]

Ooops, my brain knew what to say but the hands failed me. I didn't finish my thought.

Linux is kind of strict about major version upgrades needing to have a clean install, but I have seen conflict issues with minor versions as well.

In my defence we had siding replaced that day and the hammering was brutal.

[LeeU]

Thanks for all the help and quick response (I couldn't get back sooner due to medical problems).

Yes, I agree about the backups. As for making a back-up, I have seen a few different methods of doing it. One thing that is mentioned is backing up the /.VirtualBox directory and the /VirtualBox VMs directory. I know there are other files also. Any suggestions or tutorials? From what I have read it seems that, after doing the update, I just copy the backed up the files in the directories, and the current OS and its software "should" run properly. Is that correct?

[mpack]

.VirtualBox is obsolete(v3) advice. For v4 VMs it's best to back up the VM folders individually. They are all located by default - but not necessity - in "VirtualBox VMs".

[LeeU]

Thanks! I only use Windows XP as a guest so the "Windows XP" directory under "VirtualBox VMs" would be all of it? (You said "... but not necessity ..." so I just want to make sure there are not anymore any other place.)

[mpack]

Yes, the "Windows XP" folder should contain everything you need, unless you yourself explicitly located the main disks outside this folder.

By "not necessity" I meant that VirtualBox is quite flexible and does what you tell it: "VirtualBox VMs" is a default, but the folder for new VM is changeable in File|Preferences, and existing VMs can be relocated e.g. to different drives. You can also mount drive image files that are outside the VM folder. If you've done none of these then the "Windows XP" folder will contain everything needed to back up your VMs.

Anyway it's easy to check: the VM folder should contain a <vmname>.vbox file (VM settings), <vmname>.vdi (primary disk image), optional other VDIs, and incidental files which are backups of other files. There will also be "Logs" and "Snapshots" subfolders. The latter will contain something if you have used snapshots, saved states etc (I avoid both).

[LeeU]

Great! That sounds easy enough. I'll just copy the "Windows XP" directory back to the "VirtualBox VMs" directory when it's upgraded and I should be set to go! I appreciate all your help, mpack. Thank you.

[LeeU]

Everything went great! I made a back-up of the "VirtualBox VMs" directory and uninstalled v4.0. Then I installed v4.2 w/o any problems. When I started it a note was displayed stating the extension pack was old and asked if I wanted to upgrade. I said yes and it was upgraded w/o any problems. However, you mentioned that backing up ".VirtualBox is obsolete(v3) advice". Yet after the install I have the following files in that directory showing the date I installed the new version (along with the new extension pack).

Code: Select all

compreg.dat
Oracle_VM_VirtualBox_Extension_Pack-4.2.18.vbox-extpack
selectorwindow.log
VBoxSVC.log
VBoxSVC.log.1
VirtualBox.xml
xpti.dat

Is it supposed to be like that? Perhaps I didn't understand your statement.

[mpack]

I said that the need to backup .VirtualBox was obsolete advice, I didn't say that the folder no longer existed. The folder still exists, but no longer contains anything important.