This post has already been read 527 times!

Objectives

To develop and test in distributed environment you might use virtualizing tool like VirtualBox to imitate the environment of where number of servers and complex networks resides. But still, you have to move around through VM windows. In order to access all virtual servers using SSH just like we do in the real world, several things should be done first.
-Setup Host-only Networking
-Configure guest OS

Requirements

To achieve the goal, a virtualization tool (VirtualBox will be used here) and a little bit of networking knowledge is necessary which will be handled below. Of course you need your own laptop and Linux server OS for guest VMs.
virtualbox

Network configuration

-Separate network is necessary for host OS to access guest VMs
-To do that, each guest VMs should have two network adapters
-One is for guest VM to access outbound network, namely NAT adapter
-Another is for host OS to access each guest VM, namely Host-only adapter

virtualdomain

NAT (Network Address Translation)

-NAT feature is included in most of our home routers.
-It creates a single separate sub network below the inbound IP (public IP) so that number of machines can get an internet access and can share with each other too.
-But in VirtualBox, NAT is attached to each VM which is so called ‘Basic NAT’ that does one-to-one translation, and in contrast home routers do one-to-many translation.
-That’s why with default adapters for VMs, they can’t see each other, even from the host.
-Actually, IP, Gateway, DNS is somewhat ‘hard coded’ in VirtualBox’s NAT Adapter.

isp_hostos

Host-only Networking

-NAT is useful for guest VMs to access outbound network but as it is treated as a separate network, there is no way for host OS to access each guest OS.
-Bridged networking is used to handle this problem in real world, but it implies complexity.
-Host-only networking is kind of hybrid between internal and bridged networking.
-In VirtualBox (Host), Host-only network is a gateway for host (external network) to access guest VMs (internal network) to communicate with each other. So, it doesn’t need to be created as many the number of guest VMs.

hostonlynetwork

Considerations

Each NAT adapters and Host-only adapter should not reside in same sub-network

-eth0 -10.0.2.15 and eth1-10.0.2.12 wouldn’t work
-eth0 -10.0.2.15 and eth1-10.1.2.11 is good
-Where eth0 is for NAT and eth1 is for Host-only

Each VM should have different host name.

-VM1 : ubuntu1, VM2 : ubuntu2
-“$ sudo hostname ubuntu2” on new VM and reboot
-Make sure to set different MAC address for new VM
-Rather installing a fresh new VM, use clone feature in VirtualBox
-First, take a snapshot of well setup VM and make a clone
-At clone, check ‘Reinitialize the MAC address of all network cards’ option

After booting second VM, reset ‘udev’ network rules to set new IPs properly

-Remove /etc/udev/rules.d/70-persistent-net.rules (recreated at new boot)
-Check ‘ifconfig’ for eth0 and eth1

Use static IP rather than DHCP on Host-only Network and set host alias.

-IP of Host-only adapter will change when guest VM reboots, so turn off DHCP in VirtualBox
-When guest IPs are fixed define an alias for each guest and configure hosts file in host OS

networkingbetweenhostandguestvmsinvirtualbox-120409045512-phpapp02

Leave a Reply

Post Navigation