virtualbox.org

NEW 2.2.0 ON vista x64 host network problem :

1. my system is vista sp1 x64 host , install 2.1.4 before , and i upgrade to 2.2.0 by install

2. i try to use bridged network can't work , I got a error message :

VERR_SUPDRV_COMPONENT_NOT_FOUND

3. search in the forums , i repair the virtualbox , still can't work

4. so change to nat mode , but can;t get ip in dhcp

First run the VBox install in administrator mode. Right click on the VBox.exe and left click on run as administrator.
Then select repair, and answer yes (OK) to all of the prompts.
Once the install is done you will need to reboot the PC.
After this change the setting to Bridged if it is not already there in the VBox GUI.
Then try your guest.
If this still does not work and you decide to use NAT be aware that you will need to setup the addressing scheme yourself.
There appears to be a problem with DHCP and NAT in this version.

Host Vista 64 all current updates / drivers - Processor i7 with 16 gig of RAM
All guest vm's fully operational under VBox 2.1.4 as either Host-Interface (manually assigned ip to current host network) and NAT

Vbox 2.2.0 updates seems to have broken the DHCP functionality of NAT for MS windows OS's OpenSolaris, Ubuntu Workstation and Ubuntu Server guest vm's continue to operate configured as NAT.

The new network feature "Bridged Network" seems to have replaced the previous "Host Interface" on all of the vm's previously configred as "Host Interface".

The new "Host-only Network" option does not seem to work for guest vm's that are running Windows OS. I did not try any others.

The new Host-Only - network configuration does correclty provide dhcp addresses to windows guest vm's, but, there is no way to set the default gateway or dns servers for the Host-Only DHCP server (via a gui). When the Host-Only DHCP server is enabled or disabled you can not manually set the ip address to a network, gateway and DNS and have it function properly.

Can I easily return to the VirtualBox 2.1.4?

Some people have been able to and some not. Here is your best chance suggestions below:
Make sure that all guests are shut down and not in a saved state.
Start the VBox install again but this time right click and tell it to run as the administrator.
You will be given a screen that asks if you want to repair or uninstall.
Select uninstall. If you receive any errors you will ne to manually finish the downgrade.

There are (2) xml files that were saved whe you upgraded. One is in the .virtualbox folder that holds the program xml. The other(s) are in .virtualbox/machine/*** these will all have .bak at the end of the file. You should be able to figure it out. Just remove (cut and paste to a different place) the one that says just xml to A different place and remove the bak from the other one.

Perry
I did not refresh the board or check before I submitted my post. I am first trying your reccomended process of reinstallation as the administrator.
I am just about to reboot my Vista64 Host.
Thanks.
=====
I did the reinstall as Admin and had no luck with anything.
NAT did continue to work with with OpenSolaris and Ubuntu guest machines. Just windows guests were killed.