AIX虚拟机相关资料

之前有兄弟问道AIX的虚拟机的问题，在内网找了点资料，希望对大家有用：
鉴于本人未亲自试验，所以不能给大家更多详细资料，以下为内网wiki资料：


Quick Start Guide to SystemSim

Here is a quick start guide to getting SystemSim (aka Mambo) installed and running on your system. The following steps describe to how download a Mambo nightly build, install it on your system, and get it running.
Step 1. Determine which build you want.

To start, you need to know which target machine you want to run, e.g. p7 or q7 (Prism).

Next you must determine the architecture (i686, x86_64, ppc, or ppc64), OS (Linux, AIX, or Mac/OS), and version of Tcl for your system. The first two are usually easily obtained from uname -a.

$ uname -a
Linux ausnetx51 2.6.34-rc4-5-default #1 SMP Wed Apr 14 10:27:31 CDT 2010 x86_64 x86_64 x86_64 GNU/Linux

Determining the version of Tcl can be a little more difficult. Most Linux distros have migrated to Tcl 8.5, but some (e.g. Ubuntu) are still clinging to Tcl 8.4. If the tcl shell, tclsh, is in your path, then you can just use this command:

$ echo "puts \$tcl_version" | tclsh
8.5

Step 2. Find the build on the Nightly Builds page.

Now go to the nightly builds page (http://mambo.austin.ibm.com/nightly) and find a recent build for your architecture, OS, and Tcl version. Don't be too concerned about matching the Linux Distro - most of the build machines run some RedHat variant, but the builds from these systems typically work fine with other distros as long as the Tcl/Tk version matches. A short regression test is run on each build to determine if it is healthy, and results of this test are displayed along with the build. Be suspicious of any build that does not pass this short regression.

As an alternative to the nightly builds page, we now also publish the nightly build images on the mambo GSA project page at /gsa/ausgsa/projecgts/m/mambo/nightly.
Step 3. Download and unpack the build.

Download the build to your machine using your browser or with wget and un-tgz it into an appropriate directory (you'll need a lot of space for the simulator and images, so you probably want to put this on a local disk).
PS：以下的地址如果命令不能用，可以到：http://mambo.austin.ibm.com/mambo-bin/date.cgi 下载对应版本，
$ cd /local/mydir
$ wget http://mambo.austin.ibm.com/nigh ... -gcc-arlx221.tar.gz
$ tar -xzvf systemsim-p7-release.x86_64-Linux-Fedora_release_10-gcc-arlx221.tar.gz

To obtain the corresponding build from gsa rather than the mambo http server:

$ gsa_login
$ cp /gsa/ausgsa/projects/m/mambo/nightly/p7/2010_08_12/systemsim-p7-release.x86_64-Linux-Fedora_release_10-gcc-arlx221.tar.gz .

Step 4. Get images

Now you have the simulator unpacked. If you are going to run standalone programs, this is all you need, but most folks want to boot and run Linux or AIX, and for that you need images.

In some cases you can grab the images the Mambo team uses for regressions. Check the make targets in the 'images/<machine-name>' subdirectory to see if any of these may fit the bill. You should try to be very selective in choosing and image target, since this will likely result in the files being copied over the network to your machine, and choosing too broad a target could copy many files needlessly.

As an example, for p7 you could choose the fedora target in the images/p7/linux Makefile.

$ make -C images/p7/linux fedora
make: Entering directory `/opt2/home/mkistler/exp/systemsim-p7-release/images/p7/linux'
receiving file list ...
1 file to consider
vmlinux-2.6.30-systemsim
     7847523 100%    9.51MB/s    0:00:00 (xfer#1, to-check=0/1)

sent 42 bytes  received 2793041 bytes  1862055.33 bytes/sec
total size is 7847523  speedup is 2.81
receiving file list ...
1 file to consider
f10_sysroot_disk
  5033164800 100%   10.85MB/s    0:07:22 (xfer#1, to-check=0/1)

sent 42 bytes  received 1371489819 bytes  3092423.59 bytes/sec
total size is 5033164800  speedup is 3.67
make: Leaving directory `/opt2/home/mkistler/exp/systemsim-p7-release/images/p7/linux'

This will copy 2 files, one of which is a sizable root disk image and takes about 8 minutes.

Other places you may be able to get images:

    * /gsa/ausgsa/projects/m/mambo

Step 5. Start the simulator

The systemsim command is the recommended method for starting the simulator. You must put the bin directory of the systemsim package in your path before invoking systemsim, so that the simulator can locate its other components (libraries, scripts, images. etc.). Here is a sample invocation, which starts the simulator with only the command line interface and using the default initial run script, .systemsim.tcl, which must be in the current directory:

PATH=~/mambo/bin:$PATH systemsim

When the simulator starts, it loads an "initial run script" which typically configures and initializes the simulated machine. The name of the inital run script can be passed to systemsim with the -f option. When not specified on the command line, the simulator will use the default initial run script of .systemsim.tcl. The name of the initial run script can contain an absolute or relative path. Initial run scripts with a relative path are located starting with the current directory. In particular, the simulator expects to find the default initial run script, .systemsim.tcl, in the current directory.

To run the cell version of the simulator with the gui, using the initial run script myrun.tcl, issue

PATH=~/mambo/bin:$PATH systemsim -g -f myrun.tcl

Troubleshooting
Missing BLT

If you get a message like the following when attempting to start the simulator:

/home/mkistler/systemsim-p7-release/bin/systemsim-p7: error while loading shared libraries:
  libBLT24.so: cannot open shared object file: No such file or directory

this means that this build requires the BLT library to be available. There are two ways to resolve this problem

   1. Install the BLT package on your system. For many systems, this can be done with yum or apt-get. If BLT is not supplied by your distro, you may need to go searching for a compatible package, or build from source.
   2. Pick a different nightly build that is configured with "--disable-gui". Check the configure line in the build log to see exactly how the build on each machine is configured. Of course, if you choose this option, you will not be able to use the GUI interface to the simulator.




之前有兄弟问道AIX的虚拟机的问题，在内网找了点资料，希望对大家有用：
鉴于本人未亲自试验，所以不能给大家更多详细资料，以下为内网wiki资料：


Quick Start Guide to SystemSim

Here is a quick start guide to getting SystemSim (aka Mambo) installed and running on your system. The following steps describe to how download a Mambo nightly build, install it on your system, and get it running.
Step 1. Determine which build you want.

To start, you need to know which target machine you want to run, e.g. p7 or q7 (Prism).

Next you must determine the architecture (i686, x86_64, ppc, or ppc64), OS (Linux, AIX, or Mac/OS), and version of Tcl for your system. The first two are usually easily obtained from uname -a.

$ uname -a
Linux ausnetx51 2.6.34-rc4-5-default #1 SMP Wed Apr 14 10:27:31 CDT 2010 x86_64 x86_64 x86_64 GNU/Linux

Determining the version of Tcl can be a little more difficult. Most Linux distros have migrated to Tcl 8.5, but some (e.g. Ubuntu) are still clinging to Tcl 8.4. If the tcl shell, tclsh, is in your path, then you can just use this command:

$ echo "puts \$tcl_version" | tclsh
8.5

Step 2. Find the build on the Nightly Builds page.

Now go to the nightly builds page (http://mambo.austin.ibm.com/nightly) and find a recent build for your architecture, OS, and Tcl version. Don't be too concerned about matching the Linux Distro - most of the build machines run some RedHat variant, but the builds from these systems typically work fine with other distros as long as the Tcl/Tk version matches. A short regression test is run on each build to determine if it is healthy, and results of this test are displayed along with the build. Be suspicious of any build that does not pass this short regression.

As an alternative to the nightly builds page, we now also publish the nightly build images on the mambo GSA project page at /gsa/ausgsa/projecgts/m/mambo/nightly.
Step 3. Download and unpack the build.

Download the build to your machine using your browser or with wget and un-tgz it into an appropriate directory (you'll need a lot of space for the simulator and images, so you probably want to put this on a local disk).
PS：以下的地址如果命令不能用，可以到：http://mambo.austin.ibm.com/mambo-bin/date.cgi 下载对应版本，
$ cd /local/mydir
$ wget http://mambo.austin.ibm.com/nigh ... -gcc-arlx221.tar.gz
$ tar -xzvf systemsim-p7-release.x86_64-Linux-Fedora_release_10-gcc-arlx221.tar.gz

To obtain the corresponding build from gsa rather than the mambo http server:

$ gsa_login
$ cp /gsa/ausgsa/projects/m/mambo/nightly/p7/2010_08_12/systemsim-p7-release.x86_64-Linux-Fedora_release_10-gcc-arlx221.tar.gz .

Step 4. Get images

Now you have the simulator unpacked. If you are going to run standalone programs, this is all you need, but most folks want to boot and run Linux or AIX, and for that you need images.

In some cases you can grab the images the Mambo team uses for regressions. Check the make targets in the 'images/<machine-name>' subdirectory to see if any of these may fit the bill. You should try to be very selective in choosing and image target, since this will likely result in the files being copied over the network to your machine, and choosing too broad a target could copy many files needlessly.

As an example, for p7 you could choose the fedora target in the images/p7/linux Makefile.

$ make -C images/p7/linux fedora
make: Entering directory `/opt2/home/mkistler/exp/systemsim-p7-release/images/p7/linux'
receiving file list ...
1 file to consider
vmlinux-2.6.30-systemsim
     7847523 100%    9.51MB/s    0:00:00 (xfer#1, to-check=0/1)

sent 42 bytes  received 2793041 bytes  1862055.33 bytes/sec
total size is 7847523  speedup is 2.81
receiving file list ...
1 file to consider
f10_sysroot_disk
  5033164800 100%   10.85MB/s    0:07:22 (xfer#1, to-check=0/1)

sent 42 bytes  received 1371489819 bytes  3092423.59 bytes/sec
total size is 5033164800  speedup is 3.67
make: Leaving directory `/opt2/home/mkistler/exp/systemsim-p7-release/images/p7/linux'

This will copy 2 files, one of which is a sizable root disk image and takes about 8 minutes.

Other places you may be able to get images:

    * /gsa/ausgsa/projects/m/mambo

Step 5. Start the simulator

The systemsim command is the recommended method for starting the simulator. You must put the bin directory of the systemsim package in your path before invoking systemsim, so that the simulator can locate its other components (libraries, scripts, images. etc.). Here is a sample invocation, which starts the simulator with only the command line interface and using the default initial run script, .systemsim.tcl, which must be in the current directory:

PATH=~/mambo/bin:$PATH systemsim

When the simulator starts, it loads an "initial run script" which typically configures and initializes the simulated machine. The name of the inital run script can be passed to systemsim with the -f option. When not specified on the command line, the simulator will use the default initial run script of .systemsim.tcl. The name of the initial run script can contain an absolute or relative path. Initial run scripts with a relative path are located starting with the current directory. In particular, the simulator expects to find the default initial run script, .systemsim.tcl, in the current directory.

To run the cell version of the simulator with the gui, using the initial run script myrun.tcl, issue

PATH=~/mambo/bin:$PATH systemsim -g -f myrun.tcl

Troubleshooting
Missing BLT

If you get a message like the following when attempting to start the simulator:

/home/mkistler/systemsim-p7-release/bin/systemsim-p7: error while loading shared libraries:
  libBLT24.so: cannot open shared object file: No such file or directory

this means that this build requires the BLT library to be available. There are two ways to resolve this problem

   1. Install the BLT package on your system. For many systems, this can be done with yum or apt-get. If BLT is not supplied by your distro, you may need to go searching for a compatible package, or build from source.
   2. Pick a different nightly build that is configured with "--disable-gui". Check the configure line in the build log to see exactly how the build on each machine is configured. Of course, if you choose this option, you will not be able to use the GUI interface to the simulator.