All That is Gold Does Not Glitter

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

[0] Comments

Post a comment

Like this post?

Posted at 11:50AM Jul 04, 2008 by atishay in solaris
Tags: solaris virtualbox

Enable remote login after installing trusted extensions on Solaris

Thursday Nov 29, 2007

I got this from Jan Parcel, a sun colleague. I think it is quite useful

In most cases step 3,4 and 5(svcadm enable rlogin) suffice.

1.  Keep root as a user (it can ALSO be a role, you can add it as a role to
  users without making root a role.
  
   (by adding roles=root to the user's line in /etc/user_attr)
   
2.  Keep 0.0.0.0 as admin_low in /etc/security/tsol/tnrhdb

3.  As with all Solaris systems, comment out the CONSOLE entry in
   /etc/default/login
   
4.  Make these changes to /etc/pam.conf:

    --  add information to allow rlogin, note USE TABS not spaces.

       Modify /etc/pam.conf
       From:   other   account requisite       pam_roles.so.1
       To:     other   account requisite       pam_roles.so.1 allow_remote

       From:   other   account required  pam_tsol_account.so.1
       To:     other   account required  pam_tsol_account.so.1 allow_unlabeled


5.  As with all Solaris systems, re-enable rlogin via svcadm, or just reboot.
I always reboot.