[Solved] Upgraded to 3.0.2, now VirtuabBox won't read my con

[starfry]

Hello, I have just upgraded vb 2.2 to 3.0.2. It won't start, reporting errors:


Could not load the settings file '/home/myusr/.VirtualBox/VirtualBox.xml'.
Cannot convert settings from version '1.7-linux'.
The source version is not supported.


Result Code:
0x80004005
Component:
VirtualBox
Interface:
IVirtualBox {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667}

If I move ~/.VirtualBox out of the way it starts ok. However I can't do this as I have loads of VMs already existant.

It seems there is a compatibility problem where v2 config files can not be read by v3. This seems surprising and I can't find any information confirming this. I really need to solve this one because I have several VMs already that I need to continue using...

This is on Ubuntu Hardy LTS 8.04 Destop 64 bit.

Any pointers how to fix this greatly appreciated...

[vbox4me2]

Load the old and a new xml next to each other in VIM/gedit and manually add the VM's to the 3.0.2 format? or re-create the VM's and attach VDI's to them?

[starfry]

Yes I was planning on that as a last resort if no solution exists.

I am surprised that the config is not backward compatible - I could not find any mention of this anywhere.

[vbox4me2]

It should be compatible but 3.0.2 thinks you are using '1.7-linux' and not 2.2

[starfry]

3.0.2 thinks you are using '1.7-linux' and not 2.2

Why would that be?

I guess there is a tag in the xml that states version. Could I just change it? What would I change it to ? "2.2-linux", maybe ?

(I'm away from the machine atm so can't look - apologies if there is an obvious answer)

[greenpossum]

Odd, I have 1.7-linux too and it works fine with 3.0.2. Here are the first few lines of my VirtualBox.xml file:

Code: Select all

<?xml version="1.0"?>
<!-- Automatically converted from version '1.6-linux' -->
<!-- Automatically converted from version '1.5-linux' -->
<!-- Automatically converted from version '1.4-linux' -->
<!-- Automatically converted from version '1.3-linux' -->
<!-- Sun xVM VirtualBox Global Configuration -->
<VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.7-linux">

You're sure you didn't damage the config file in some way? Or does it have no permissions for you?

[starfry]

Hmmm, I'll have to check - I'm pretty sure I have access to the files. It was all working before I did the update (apt-get install virtualbox) which said it would remove virtualbox-2.2 and install virtualbox. After that I rebooted (to be sure) and then I have this problem. It does seem very strange...

[starfry]

Well I feel like a bit of a duffer now

My "upgrade" actually took me back to 1.6.6!!! I have just re-installed explicitly stating Virtualbox 3 and I am running happily on 3.0.2 with my existing config.

Thanks to everyone who replied with suggestions - they helped me realise my own stupidity.

Lesson learnt... Don't perform upgrades late on Sunday Night