virtualbox.org

I'm not normally one to post in forums, prefer to help myself, I'm good with google, but I've literally spent days tearing my hair out on this.

After giving up with VB 2.0.x (constant networking problems and then video driver went blotchy and unuseable) I've started with a fresh 2.1.0 installation, and a totally fresh Centos 5.2 guest install from ISOs.

I have an XP host and Centos 5.2 guest. When the guest is using the "NAT" interface it works fine, it gets an IP of 10.0.2.15 (Bcast 10.0.2.255 Mask 255.255.255.0) and it can see the internet so is fine as a "stand alone" operating system, but it can't see the host as it's on it own subnet the host can't see (10.0.2.x).

So I know (or, rather, I conclude) that I need to use "Host Interface". I select this, and can choose from my laptop's ethernet or wireless interfaces (also an Orinoco card driver I've used before and my Windows mobile device, neither of which are connected).

I choose the ethernet device, restart the guest. "Determining IP information for eth0" takes a long time and fails. My XP network connections reports "Local Area Connection - Network cable unplugged - Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Controller".

I have also tried this using "Host Interface" as a second interface and leaving NAT on the first interface but no cigar.

I have RTFM so many times my head is hurting. What am I missing?

TIA.

Depressed!

I'm having the same problem. In previoua versions, in Host interface I was able to add "virtual interfaces" to the list, and later do a bridge so they could connect to internet and also have an IP address on the same subnet... but that option seems to be missing now... is it gone for good? is there any other alternative?
(in my case the host is vista64)

thanks!

Diegolaz, stick to one topic. Don't cross post your questions.

Neov,

Since 2.1.0, the HIF system changed. In order to use it properly, you must make sure that there is a connection on the interface. If the cable is unplugged, the NIC is turned off and it's config is removed. If you want to get a Host <> Guest connection, install the MS loopback adapter. See the VirtualBox FAQ for more info.

You are a true gentleman. That nailed it.

Can I offer the following observations:

1) The 2.1 manual page for host interface doesn't even mention a loopback adapter

2) The FAQ page says this:

Q: I use >= 2.1.0 and want to use the old Host Interface method, how can I do this?
A: You have to create virtual interfaces and bridge them like you used to do. Linux has the TAP interfaces you can create with the uml-utilities package. For Windows, please see MS KB839013 - How to Install the Loopback Adapter in XP for more information. Vista users should have the same method, but if you don't, please look for other ways, like using DevCon.

I read this FAQ item. It says "use the OLD host interface method", so I took that to mean, to use functionality that doesn't come standard with 2.1. In 2.0 VB installed an adapter in my networking, and 2.1 removed it, but in the settings for a VB it lets you choose HI, so I took that to mean that VB knows what it's doing, and that is the NEW host interface method.

For the record, what exactly is the new "host interface" method? The NAT option? If so, can I suggest renaming this FAQ item to:

"I use >= 2.1 and I want to use the Host Interface method".

The 'new' method no longer involves virtual interfaces and bridges, you can access the interface directly like on MS VPC.