Dec. 17, 2008
Being all excited about Virtualbox 2.1 being released today I downloaded and installed it on my Ubuntu laptop. As quite a few changes have been made, including changes to networking, I was not very surprised to see that the configuration files needed to be upgraded by the application. However, I was surprised that 50% of them failed! I tracked the problem down to the machines I am running with custom startup and shutdown scripts for my host interfaces. It seems as the conversion failed to properly convert these machines as these scripts can no longer be used with host interfaces in the application.
According to the changelog:
“New Host Interface Networking implementations for Windows and Linux hosts with easier setup (replaces TUN/TAP on Linux and manual bridging on Windows)”
I saw that the same issue I am having was reported here three hours ago. So if you are seeing a number of machines that fail to convert with the following message, this fix is for you.
“Assertion failed: [!name.isNull()] at ‘/home/vbox/vbox-2.1.0/src/VBox/Main/NetworkAdapterImpl.cpp’ (1068) in nsresult NetworkAdapter::loadSettings(const settings::Key&). Please contact the product vendor!.”
In order to fix the machines reporting this problem you need to:
- Enter the directory of the Machine configuration, in my case the users name is patrik and the machine name is XP which results in the following directory /home/patrik/.VirtualBox/Machines/XP/
- Make a copy/backup of the xml file in this directory and open it with a suitable editor
- Look for any lines containing “<HostInterface TAPSetup” and simply delete it
- If you have Virtualbox running simply press the refresh button of that machine and it should now convert
Obviously, you will need to setup the interface again using the configuration editor.
5 Responses to “Virtualbox 2.1, new release, new problems”
Hi,
I had the same problem.
Followed your suggestion and it worked.
Thanks.
By Bruno on Dec 18, 2008
Thanks, the fix worked!
By Roberto Bechtlufft on Dec 20, 2008
I was using a script to do bridged networking, so I also had to change the network settings.
Settings->network->Attached to: Host Interface
By John on Dec 22, 2008
Thanks for the Post.
However My WindowsXP.xml did not have this
“<HostInterface TAPSetup” setting.
I played around with the adapter settings however still having the exact same problem you have mentioned above.
Any help would be appreciated.
Mike
By Mike on Jan 15, 2009
Resolution if you don’t have the “<HostInterface TAPSetup” setting in your file.
Create a new Windows XP Virtual Machine, when prompted for the Virtual disk use your existing image.
This will then create all the new .xml settings based on the new version.
This then ran my old Virtual image.
Cheers
Mike
By Mike on Jan 15, 2009