tkwm wrote:Isn't it possible to solve your problem by using shared folders and the localhost (127.0.0.1) url?
Shared folders work fine, that's not my problem. I need the following to work:
Guest (Win Server 2K3) runs IIS and SQL Server and has an IP of, say, 192.168.0.2.
Host (Leopard) runs Apache and MySQL has IP 192.168.0.1.
When I type http://192.168.0.2
in the HOST web browser, it should bring up the site hosted on IIS on the Guest.
When I type http://192.168.0.1
into the GUEST web browser, it should bring up the site hosted on Apache on the Host.
The only way to make this work is to manually configure AirPort or Ethernet (both are physical network adapters) with the IP 192.168.0.1. That makes absolutely no sense at all.
This functionality should not require use of any physical interface on the host.
There should be some kind of "Virtual Ethernet" adapter for OS X (an equivalent to the Microsoft Loopback Adapter on Windows) that I can configure in System Preferences with whatever IP address I want, and then be able to select this virtual adapter in VirtualBox. Like I said before, I tried TUNTAP but it does not expose the tap devices to System Preferences, and therefore VBox doesn't pick them up as selectable interfaces.
Does it make sense what I'm trying to do? The Linux version of VB has this bridging capability -- please note "6.8 Host Interface Networking and bridging on Linux hosts" and "6.8.1 Permanent host interfaces and bridging" in the VBox manual on page 78.
Why can I not do this simple thing under OS X? Why aren't the VBoxAddIF and VBoxDeleteIF utilities provided on the OS X distro? Why has this functionality been completely left out of the OS X version? OS X is based on Unix... how difficult is it really to port the bridging capability over to OS X?
There must be a zillion web developers out there using MacBook Pros who need to run Windows virtually for testing purposes, and bridging should be a basic function of any VM software. Other than this, VirtualBox is totally awesome...
...but if I'm out in the field and want to demo some of my sites without accessing someone else's network, why should I have to resort to a totally ridiculous workaround every time when this feature is standard on other systems such as VMWare Fusion and the Linux version of VBox?