Home > linux > Building a Clustered Shared SubNetwork with VirtualBox 3.0.2 (Ubuntu 9.04 Host + Ubuntu 9.04 and Windows XP Guests)

Building a Clustered Shared SubNetwork with VirtualBox 3.0.2 (Ubuntu 9.04 Host + Ubuntu 9.04 and Windows XP Guests)


Problem: to have a cluster of machines to work for development using VirtualBox guests. That is, I want to be able to have different operating systems running on my own development box, having each of the machines sharing the same Internet connection (my main one) and acquiring IP address from the same DHCP server (aka wireless router, or whatever…)

Description: Finally, something to make all of us happy! VirtualBox 3.0.2 delivers smooth support to shared Nat and Subnetwork outside-the-box!!! This has always been a dream of mine to use VirtualBox for such agility of having as much development machines as I can (your host memory).
What I could accomplished tonight was the setup of a shared subnetwork between my host Ubuntu 9.04 and my guests on Ubuntu 9.04 and Windows XP SP2. Everything I did was to setup network cards from each of my guests to use the network interface as a Bridged Adapter, and choose the one I have Internet connectivity. By the way, the connectivity I am using is my wireless card.
This can help anyone who needs different boxes and installations of machines to develop and test applications that depend on the network, shared resources, etc. For example, I need to build a Sensor Network that sends collected data to the main data center as my thesis simplest workspace. On a single box, my development environment is contains source-code for both the Sensors and the Main node. However, with the use of Subversion and SCP I can transfer artifacts over between the boxes and still test the transport layer of my sensor network.
Setup: To better describe what I have, here’s the description of each member of my network made with VirtualBox 3.0.2:
mdesales@mdesales-laptop:~$ ifconfig
 eth0  Link encap:Ethernet HWaddr 00:11:25:81:48:6d 
            UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
 eth1  Link encap:Ethernet HWaddr 00:0e:35:c6:5a:0f
             inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
             inet6 addr: fe80::20e:35ff:fec6:5a0f/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
            RX packets:583718 errors:235 dropped:235 overruns:0 frame:0
            TX packets:316625 errors:0 dropped:5 overruns:0 carrier:0
            collisions:0 txqueuelen:1000
            RX bytes:763972253 (763.9 MB) TX bytes:30157656 (30.1 MB)
            Interrupt:11 Base address:0x4000 Memory:c0214000-c0214fff

Note that you will need to know which device you currently have Internet connectivity. In my case, as you can see, I have it through the eth1. I acquire IPs through my private Wireless Router DHCP, which is connected to the Cable modem, in the range of 192.168.0.100192.168.0.199.

  • Guest 1: Ubuntu 9.04 Desktop
  • Guest 2: Ubuntu 9.04 Mini
  • Guest 3: Windows XP SP3

For each of them, I just configured the network device to use the Bridged Interface, and choosing a correct device. To be clear, you want to choose the one you currently have Internet connection. In my case, I have on the eth1, which happens to be my wireless card. However yours can differ!

* Environment Evaluation: I’d like to ping, ssh, share resources, build a mysql cluster, hadoop grid, test my grails app, write Android App… The dream I have always had is to have my own “cloud” of pre-defined VirtualBox with the profiles of what I usually need. I must say that I can finally rest my mind! I could finally make it work…
I have mixed up 2 different projects: my thesis boxes and a Software Engineering research developed in 2 different environments (that’s why I love keeping my VirtualBox hard-disks in my backup storage for later reuse). Most of people who have tried integrating guests could only PING a machine, but not SSH, samba, etc. I got frustrated 3 or 4 months ago about the same situation and I had to settle. Anyway, the truth is that tonight I got it working without any voodoo command to turn off the firewall, to configure different tunnel… I just wanted it working… See how many people were having related problems here (http://www.savvyadmin.com/virtualbox-host-interface-networking-with-nat/)

Let’s see each machine IP address.

* Guest 2: Ubuntu 9.04 Mini: 192.168.0.100

* Guest 3: Windows XP SP3: 192.168.0.103. Note that the ping is from the Guest 2 to the Guest 3 machine!!! I had never accomplished this with previous versions of VirtualBox without reading the documentation for hours…

* Pinging the host from the Guest 2: this step I could reproduce using the voodoo steps described on other pages. Here’s an example of the guest 2 pinging the host.

* SSH from among the machines: one HUGE step was that, at this time, we can definitely SSH from each of the machines. I just installed Ubuntu with openSSH server in each of them. That’s ALL!!! I’m making an SSH connection from my machine to the Guest 2.
This is the SSH session between the Guest 2 and the Host.

The SSL connection between the hosts is done. In this screen, the user ssh from the Guest 3 (Windows) to the Guest 2 (Ubuntu).
Note that the window at far-most of the screenshot is the Host.
After testing all these features, I wanted to verify if the communication is done without no changes.
I was lucky to find out that the everything works outside-the-box, including Internet connection!!!!

Advertisements
Categories: linux
  1. quba
    July 31, 2009 at 5:04 am

    I recently came accross your blog and have been reading along. I thought I would leave my first comment. I dont know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.Margarethttp://bluetoothspeakerphone.net

  2. Mike Wood
    August 27, 2009 at 10:37 am

    What you describe here is not NAT. It's bridged network, in which case you can image as your guests physically linked to your host. The virtualbox NAT is not quit useful since your multiple guests can't connect to each other. They all assigned IP address of 10.0.2.15.

  3. Marcello de Sales
    January 5, 2010 at 10:51 pm

    I haven't seen this post Mike… But if you see the screenshots, all the guest OS's have different IP addresses acquired from the main DHCP reached from the host OS. Maybe you could not see, but ALL of the guest OSs can connect to each 🙂 I've been using this strategy on different research projects 🙂

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: