virtualbox.org

I'm running VB 3.2.10 and am interested in upgrading to the 4.02 version. I don't see any information on the steps to take, either in the manual or the forum (I searched "upgrade steps for 4.02").

Do I just download the .exe for 4.02 and run it and the upgrade takes care of itself? Do I have to uninstall my previous version first? Are there other 'gotchas' that I need to know to upgrade? It would be good to have a section on this in the 4.02 manual.

Sorry if I missed the answers somewhere. I did look.

It depends if you would like to preserve the v3.2 folder structure (then just install v4.0 over existing installation) or you would like to migrate to v4.0 folder structure (uninstall the product).

Because one of the best new feature of v4.0 is folder structure change (you can now copy a folder to new location/computer and you get new virtual machine up and running in no time).

I did the following:
1. copy .vdi file from existing virtual machine to save location
2. uninstall vbox v3.2 and clean all left-over folders (asuming you are on Windows host): delete folders c:\program files\oracle and c:\document and settings\[user]\.VirtualBox
3. install vbox 4.0
4. create virtual machine and on window asking to create new disk or exiting disk copy with Windows Explorer a .vdi file to location C:\Documents and Settings\Igor\VirtualBox VMs\[your_machine_name]
and then select "existing disk" and point to this newly copied .vdi file
5. that's it.

Thanks.

Do I also copy the "Machines" folder?

What about snapshots? I have lots of snapshots with the VMs, which I use for testing under different configurations.

IMHO it's safest to uninstall the old version first. The only "gotcha" with the v4 install is that you must remember to install USB support as an additional step. At least I think you have to do that, but I've never actually checked what happens if you don't.

Contrary to the other advice, I recommend that you do NOT delete the contents of your old .VirtualBox folder. I can't think of any good reason for doing so, based on the goals you've mentioned so far. When you start up v4 it should find the old VMs where you left them.

It might also be wise to backup your PC with Acronis or similar before you start. That way you can easily retreat if disaster strikes.

vberic wrote:Thanks.

Do I also copy the "Machines" folder?

What about snapshots? I have lots of snapshots with the VMs, which I use for testing under different configurations.

The best thing is to create a backup of .VirtualBox directory before starting (like mpack suggested - prevents some disaster), so you can get back to previous state.
But you have to know you need to do steps described above is you would like to CHANGE to vbox 4.0 folder structure, if not then just install vbox 4.0 over existing install and everything should work.

If you would like to CHANGE folder structure to v4.0 layout:
1. I did a print screen of my machine and then manually created the same settings (so I didn't need any Machine folders)
2. I have deleted all snapshots, so having only single .vdi file - if you would like to preserve your snapshots then I strongly suggest to NOT follow my suggestions, but instead just install VBox 4.0 over existing vbox 3.* install and just PRESERVE existing vbox 3.* folder layout.

There is this http://blogs.sun.com/fatbloke/entry/vir ... tion_files
But imported Windows systems become not genuine, so hold onto the original vms as the imports will have "-1" appended to the names and the virtual HDs will have generated names.
Then the tedium starts
1. For an old VM, release its virtual HD(s)
2. For the vm "-1", release its imported virtual HD(s) and attach the old's HD(s)
3. Remove the generated-name imported virtual HD(s)
<sigh>
Once satisfied, the old vms may be deleted and the imports renamed to lose the "-1" by editing the name via Settings
Best!