Page 1 of 1

Upgrade problems from VB 2.1.4 to 2.2.0 - workaround tip

Posted: 14. Apr 2009, 23:47
by hansa
Hello!

As many others, I got some problems after upgrading from VB 2.1.4 to 2.2.0 and this is how I fixed it:
I run the system on Windows XP SP3 with 4GB of RAM and on Vista SP1 with 4 GB RAM.

1. Run the upgrade - it has some problems (missing VirtualBox Host Interface Networking Driver on the different network connections...)
2. Reboot
3. Run the upgrade again and the choose repair
4. Reboot (this is the world of Windows...)
5. Try to add a NAT connection.. it fails, the "GUI" doesn't register the change...then do this:
5a. Go to "C:\Documents and Settings\..your username...\.VirtualBox\Machines\"
5b. Hopefully you got an older xml file called somename.bak, open it and locate this part of the XML file:
(If not set the "HostInterface name" equals the device name (not the name) of your active network connection, or the network connection you are going to use with VB)

<Network>
<Adapter slot="0" enabled="true" MACAddress="080027BF4F9C" cable="true" speed="0" type="Am79C973">
<HostInterface name="NVIDIA nForce MCP Networking Controller"/>
</Adapter>
<Adapter slot="1" enabled="false" MACAddress="0800274DE3F7" cable="true" speed="0" type="Am79C973"/>
<Adapter slot="2" enabled="false" MACAddress="08002701FCDA" cable="true" speed="0" type="Am79C973"/>
<Adapter slot="3" enabled="false" MACAddress="080027778A42" cable="true" speed="0" type="Am79C973"/>
<Adapter slot="4" enabled="false" MACAddress="08002701BDFC" cable="true" speed="0" type="Am79C973"/>
<Adapter slot="5" enabled="false" MACAddress="080027E86D79" cable="true" speed="0" type="Am79C973"/>
<Adapter slot="6" enabled="false" MACAddress="080027467AD9" cable="true" speed="0" type="Am79C973"/>
<Adapter slot="7" enabled="false" MACAddress="0800274938A4" cable="true" speed="0" type="Am79C973"/>
</Network>

5c. The new XML file will say something like this:
<Adapter....">
</NAT>
</Adapter>

5d. Change the </NAT> to <HostInterface name="NVIDIA nForce MCP Networking Controller"/>
it will be something like this:
<Adapter....">
<HostInterface name="NVIDIA nForce MCP Networking Controller"/>
</Adapter>

"NVIDIA nForce MCP Networking Controller" is the device name (not the name) of my network connection... or the network connection you are going to use with VB

6. It looks like VB can't save the configuration. I have tried this fix on Windows XP host and Vista host and it works.

PS! If someone already posted about this subject, sorry. I haven't had the time to read all the posts.

Brg
HAJ