virtualbox.org

Hi,

I try to use bridged networking (it is the simplest to use) but when I have to choose the interface, I only can see the "Nothing selected" option. Obviously there is a network adapter in my XP to be bridged to. Under Vista I could use bridged networking with many instances of virtual machines by simply selecting the interfaces.
I have some old virtual machines whose setting I copied to my new VB configuration directory but even if I start a new virtual machine, the bridged card cannot be selected.
I already tried to hack the xml file to put the name of my existing network card but it fails to start complaning about not finding the host interface using that name.
What is wrong with VirtualBox under XP?

Sounds like a failed install of VBox. Try to re-install and select the repair method.

I had a similar problem when I installed vbox 3.0.4 on an xp machine. I noticed in my network connections window that I had some VMWare player drivers and had to uninstall VMWare first, then uninstall VBox, reboot and reinstall VBox. I could then at least select my network adaptar when creating a bridge, however, vbox is still failing to start (see thread on bridged network connections for a discussion of this).

Perryg wrote:Sounds like a failed install of VBox. Try to re-install and select the repair method.

I already tried that but the adapter is not visible (I don't have any other virtual program, the installation of my XP is very recent). I am very disappointed right now, I like VirtualBox's adapting screen resolution, Virtual PC 2007 isn't good with that.
I don't understand that if an existing adapter's name is used why VB can't start. Where else should I set the existing adapter?

You say old VMs. Are they by chance from VPC?
If so did you remove the VPC additions first?
Have you tried to install a new VM and if so does it have the the adapter of the host as a selection in the guest settings?

No, they are VirtualBox 3.0.4 images, created in Windows Vista. I reinstalled VB and tried to create a new virtual machine but the adapter cannot be selected. As I mentioned I already tried to hack the xml file of the machine but even if I copy the name of the adapter from its properties, it isn't visible for VB. What else could I do?

I have not seen this problem since we left Version 2.x but it appears that the VB network adapter is not installed.
Try to right click on the install and then run as admin then repair and reboot the host. See if this helps.

If that doesn't help, uninstall VB and install it again (as admin) and make sure the Bridged driver is marked for installation. Any questions about drivers that could make your system unstable or unusable need to be answered with "Continue Anyway".

I checked and during install I always enables the unsigned drivers to be installed and the VirtualBox Networking is also selected for install (there is no distinction of network types). I can't give any explanation why it has broken.
By running as administrator what you mean? In XP, my user has administrator privileges.

That's not the same thing. Right click on the install file and then left click on run as admin. See if this will install the drivers.
If not then uninstall it and then install as described above.

In XP there is only "Run as..." command in right click menu (Yes, I already chose "Administrator" in the drop down menu, no difference). You might have confused it with Vista.