• The VTune™ analyzer installation may fail if all users, including root, are not allowed to add new users and groups to their systems except through NIS. In this case you should create an NIS user "vtunesag" and an NIS group "vtunesag" with the following parameters:
• $ groupadd -g 28888 vtunesag
• $ useradd -u 28888 -g vtunesag -r -s /bin/false -d /sbin vtunesag
• After that, try to re-install VTune Analyzer.

• The install script hangs occasionally on some Intel® 64 systems after running install.sh and before the registration phase. If this occurs, first try running the install.sh script again. If the problem persists, copy the license file you received in the email from the Intel® Registration Center to <Install Dir>/intel/licenses (default installation directory is /opt/intel), and run the install script again. If the install still hangs and you have an Intel® Premier Support account, submit a technical support issue and refer to this SCR number. If you do not have an Intel Premier Support account, go to Registration Center and click the "contact technical support" link at the bottom of the page to submit your issue.
  
  The VTune™ Analyzer 9.0 for Linux* can be integrated only with the 32 bit version of Eclipse 3.2.1 on Intel 64 systems. Integration into a 64-bit version of Eclipse is not supported.

• If you are installing the vtl software on a network filesystem (such as NFS or AFS), you may experience security-related installation failures, depending on how the network file system was set up. In the event of such a failure, you should first install the needed software locally (by default, the /opt/intel and /opt/sag directories, and their subdirectories), and then, after successful completion, put the software on the shared drive. To complete this process, you need to create symbolic links pointing from the local directories to the network directories. [SCR #13717]

• During installation, do not enter an installation path that contains a space; if you do, the installation will fail.

• If you install the Intel® C++ Compiler 8.1 with Eclipse integration, then install the VTune analyzer with Eclipse integration and try to run vtlec, it fails to start. You should set these environment variables prior to launching vtlec:

OTHER_JVM_BINDIR=Your JVM/bin directory (" /opt/intel/eclipsepackage/3.1.1/eclipse" by default) and OTHER_ECLIPSE_BIN=Eclipse binary file for VTune analyzer (" /opt/intel/eclipsepackage/3.1.1/eclipse" by default).

• VTune A nalyzer 9.0 for Linux* requires Eclipse* version 3.2.1. It will not work properly with another version of Eclipse.

• Intel compilers version 9.0 and earlier install an earlier version of Eclipse, therefore during the VTune analyzer installation, you must choose to install a separate version. You should not merge with an existing version of Eclipse* unless it is version 3.2.1.
• If you have installed any other tools that require an earlier version of Eclipse*, you must install a separate version of Eclipse for the VTune analyzer for Linux.

• The VTune&trade Performance Analyzer does not support the cluster filesystems Linux kernel under SuSE* Linux Enterprise Server* 9.0.

• When you run the VTune Analyzer under Eclipse for the first time, Dynamic Help indexing is performed. During this operation it is not possible to create a local tuning activity on Intel® 64 and a remote tuning activity on IA-32, Intel 64 and Itanium® processor-based systems. As a result of this action you may see an error messages like: "Error: Failed to configure the collector," "Error - Remote operation failed," "Select error before receiving bytes Error no.: (4). Connection to server lost." Wait until the indexing is finished to create the tuning activity as a workaround for this issue.
• The VTune analyzer will crash under Eclipse if you run it with BEA JRockit 1.5.0 under Red Hat* Enterprise Linux 4.0 for Intel 64. The problem occurs if the "Modify Activity before running" check box is checked at the end of the wizard. Do one of the following to avoid this situation:
• Install the errata kernel for Red Hat Enterprise Linux 4.0.
• Use Red Hat Enterprise Linux 4.0 U1
• Use the Sun JVM 1.5.0

• Eclipse 3.1.1 may hang on an Intel® IA-32 system with BEA* JRockit* 1.5.0 and Red Hat Enterprise Linux 4.0. Install the 32-bit Sun JRE v5.0 and set the path to the JRE in the environment variable OTHER_JVM_BINDIR to Sun's JVM directory as a workaround for this issue.

• You may get an error message: "An error has occurred. See error log for more details" if you have uninstalled the analyzer and reinstalled it. Delete the $HOME/.eclipse directory after the uninstall is finished.

• When you open an Eclipse workspace created with a previous version of Eclipse, you may get an error message. This is a general Eclipse issue and will be considered by eclipse.org for a future version of Eclipse. The error message is only displayed the first time you open the Eclipse workspace.

• The evaluation version of the analyzer contains all of the features of the commercial version, except you do not have the ability to open existing projects, save projects, or the ability to create or unpack a Pack and Go file. You do not need to re-install the product when you convert from the evaluation version to the commercial version. Simply copy your commercial license file into the directory specified by the INTEL_LICENSE_FILE environment variable. The default location is /opt/intel/licenses.

• In order to build the VTune analyzer Driver Kit driver for Red Flag 5.0 DC kernel compiled with the Intel® C++ Compiler you must install icclibs rpm, which provides Intel® C++ Compiler runtime libraries.
• Sampling on kernels configured with non-consecutively numbered CPUs (as seen by cat /proc/cpuinfo) is not supported.
• The VTune™ Perforrmance Analyzer 9.0 for Linux* client is not compatible with the VTune™ Perforrmance Analyzer 8.0 for Linux* vtserver. If you try to collect data using this configuration you will get an error message: Remote agent on the remote system is incompatible with this version of the VTune Performance Analyzer. Be sure you install the VTune Perforrmance Analyzer 9.0 for Linux* remote agent on the remote machine to avoid this situation. The reverse is also true. The VTune analyzer 8.0 for Linux client is not compatible with the VTune analyzer 9.0 for Linux vtserver.
• Sampling does not work on Dual-Core Intel® Itanium® 2 processor 9000 sequence-based systems with Asianux 2.0 (kernel 2.6.9-11.24AX). You should upgrade to a newer kernel which supports sampling on Dual-Core Intel Itanium 2 processor 9000 sequence-based systems.
• Sampling with BEA JRockit 1.4.2 incurs overhead > 50%. Add the following command line options to the java program to solve the problem. This is not needed for BEA JRockit 1.5.0.

  -Xjvmpi::allocs=off,monitors=off,entryexit=off

• In order for sampling to work on a Linux* 2.6 kernel, Oprofile must be enabled in the kernel. Some IA-32 UP kernels such as those in Red Hat* Red Hat Fedora* Core 2 and Core 3 distributions and in Red Hat* Enterprise Linux 4.0 do not have Oprofile enabled by default. If you are using such a kernel, we recommend that you use the IA-32 SMP kernel instead since Oprofile is enabled there. The IA-32 SMP kernel is usually provided on the Linux vendor’s install CDs. Once you’re booted into the kernel, then you may either use the default sampling driver (if it is available) or build one using the VTune analyzer driver kit. See /opt/intel/vtune/vdk/src/ README for details.
• The default kernel that comes with MontaVista Linux Carrier Grade Edition* 3.1 on IA-32 systems has mismatched kernel sources. This results in some symbols not being exported correctly, which in turn causes problems with building VTune analyzer driver kit driver for that kernel. The workaround is for customers to rebuild their kernel and then build a sampling driver for that kernel. The steps are described in the Installation Limitations section of these Release Notes.
• Sampling hotspots may show up in "Other32" for Sampling activities on MontaVista Linux-based systems. This happens because the sampling driver requires OPROFILE to be enabled and the default MontaVis ta Linux* kernel is not configured with OPROFILE enabled. To resolve this issue, either rebuild the kernel with OPROFILE support, or start the application prior to starting the sampling activity and then start collecting data. [SCR #25854]

• In Call Graph view, when trying to sort by a hierarchical column, the grid's behavior is to sort by the internal column, and not the hierarchical one - in this case simply set hierarchy off, sort by needed column, and set hierarchy on again.
• If you are upgrading your version of the VTune analyzer, after installation you may discover it is not possible to create a call graph project. To correct this issue, remove the /tmp/vtune_username/ directory, which ensures that the files in it were not created by an older version of the VTune analyzer.
• The LD_LIBRARY_PATH environment variable must not contain /lib. Including /lib in the LD_LIBRARY_PATH environment variable may cause call graph to load the wrong shared object with the application.
• The LD_LIBRARY_PATH environment variable must always contain an absolute path -- not a relative path, or Call Graph may fail to profile the application.

• Call graph support is based on binary instrumentation; therefore only instrumented functions are reported in the call graph results. There can be several reasons why a function may not be instrumented:
• There is no symbol for the function in the binary (the image is stripped).
• The first basic block of the function is smaller than 5 bytes.
• The function is inline and therefore doesn't exist in the binary.

• Statically linked executables are not fully supported. You may see problems, especially when C++ exception handling is used. To avoid this problem, dynamically link your application for Call Graph profiling.

• When specifying a module of interest for Call Graph profiling on remote machines and systems with Intel® 64 processors, make sure the module already exists. For local call graph profiling, you may specify a module of interest that does not exist initially, but will be generated during the Activity run.

• The buffer-size property name is buffer size. By default, the buffer size is set to 128MB, unless your system has less then 256MB, in this case, it is half of the physical memory. More information on the configuration file can be found in the VTune analyzer command line interface User's Guide. By default, the VTune analyzer User's Guide is located in /opt/intel/vtune/doc/users_guide/ index.htm.

• Call Graph does not support applications that use two different shared objects with the same name, even if they are located in different directories. This may cause an abnormal termination of the VTune analyzer.

• Call Graph adds the pthreads library to the instrumented application in order to profile it. Call Graph profiling does not support applications that cannot link to the pthread library into the executable.

• Using Function selection with a remote Call Graph Activity before running the Activity cause instabilities in the Eclipse GUI. To avoid this issue, run the Activity before using this functionality.

We have recently become aware of an issue with "per CPU buffering" support in the Intel® VTune™ Performance Analyzer for Linux*. You may experience any of the following symptoms on systems with more than 4 processors when per-cpu-buffering is enabled:

• skewed sampling results
• large variations in sampling results
• system crashes

We are working on characterizing the issue but until then we suggest you use this feature with caution. This feature is automatically enabled on SGI* Altix* Pro Pack 4 Service Pack 3, and SGI Altix Pro Pack 5 systems.

The feature can be manually disabled by setting the following environment variable prior to running vtl or vtlec:

SEP_PERCPU_BUFFER=0

Please check back often for updates on this issue.