VirtualBox : Setup your own Debugging Environment
Friday Jul 04, 2008
The idea is that you have a problem to fix and you don't want to play with your system. VirtualBox gives you ability to have another OS run (now onwards Guest OS) on your top your OS (now onwards Host) on which VirtualBox (now onwards VB) is installed.
Problems where you don't need networking support to solve issues, it is straightforward. When you need networking support, it is little tricky. I will mention here one way which worked for me.
- You need OpenSolaris Crossbow bits
- About Cross bow http://opensolaris.org/os/project/crossbow/
- Download http://opensolaris.org/os/project/crossbow/snapshots/
- Setup Virtual Interfaces on Solaris
- Crossbow allows you to do Network Virtualization
- We will create Virtual Network (called as vnic)
- We create vnic on top of either your ethernet (then your virtual network would behave same as your ethernet as far as networking is considered) or create a virtual network on your machine (then the network is internal to your Operating system (Host OS for Virtual Box).
- I will create Virtual Network over ethernet. This way you guest OS will get same network infrastructure as your host OS. You would want to do that in most of the cases so that your guest OS is accessible over network.
- Command to use is dladm. I don't have my laptop right now otherwise I would mentioned exact commands here. You need something like "dladm create-vnic". Please check the syntax.
- Setup VirtualBox (i..e your Guest OS)
- Once you create a vnic, you get will get a MAC address. You need to specify that MAC ID for the guest OS. This should be done under Network Adapters settings
- After this is done, your machine will get IP address if your are using DHCP. Otherwise you need a static IP which should be specified in step 2 while using dladm
I will post more details shortly. It's been pending for past 2 months now.
Happy Debugging
Like this post?
|
|
|
|
|
|
|
|
