Your kernel may be supported by the latest update. Please see the current list of distributions supported by our latest update.

If you have updated your kernel since installing the VTune analyzer, or if your kernel is new since the VTune analyzer was released, the sampling driver must be built (i.e., compiled and linked). Normally, the driver is built automatically during installation, if you have the kernel sources and a compiler installed. For detailed instructions on building the driver, see the file /opt/intel/vtune/vdk/src/doc/HOWTO-BUILD-VTUNE-DRIVER (default location) after installation.

Yes. You can get Call Graph and Sampling profiles of MPI applications using the VTune™ analyzer. For a distributed MPI application it's possible to collect sampling data only on a particular node where some part of application is executed. Just run sampling session on that node without "application to launch." However VTune was not designed to do detailed CG analyses of distributed MPI applications.

Chameleon MPI (MPICH)
You can perform CG collection only from the node where your application is started (use mpirun as a launcher, -np N mpi_app.exe as a parameter and mpi_app.exe as a module of interest). Since instrumented version of profiled application is executed on the node expect some slowdown. In some cases it might lead to discrepancies in you synchronization mechanisms.

Intel® MPI
For the Call Graph collection there is some specific. Intel® MPI launches applications with help of a daemon. VTune* during data collection tracks the hierarchy of executed processes in a special way. It cannot collect Call Graph data if Intel MPI daemon (mpdboot) is started before you run your activity. The right way is to use a special wrapper script that runs Intel MPI daemon and then your MPI application all together. Use that script as an application to launch during activity configuration. The described way gives you an opportunity to collect Call Graph data on every cluster node other than the node from where you start your application with mpiexec. Just run Intel MPI daemon under VTune setting your distributed application as a module of interest on the node where you want to collect data. Ask if you need more details.

Please review other Intel® products to speedup and analyze your distributed and shared memory applications.

http://www.intel.com/cd/software/products/asmo-na/eng/244171.htm.

Solution:

Is the VTune™ Analyzer 8.0 for Linux* compatible with Enabled Security Enhanced Linux*?
Yes. The VTune analyzer supports SELinux environment on RedHat* EL4, Novell* SuSE* EL9, Fedora* Core 2.

You can effectively use the VTune analyzer for collecting both sampling and callgraph profiling data with SELinux enabled by default. Due to some nondefault rigor permission rules, there might be some issues using VTune.

To check if SELinux is enabled/disabled, run the following command selinuxenabled; echo $?. It should report zero value if selinux is enabled.

To disable SELinux, follow these steps:

1. Set the SELINUX variable in /etc/selinux/config file to "disabled" and reboot your system.
2. Add "selinux=0" kernel argument in lilo.conf or grub.conf files.
   Note: For one time, boot Linux with "selinux=0" kernel argument.

Note: VTune CALL GRAPH collection doesn't work with recent SELinux implementation (v1.23) that is a part of RedHat distributive starting from FC4.0. To collect CALL GRAPH, you need to disable SELinux.

Symptom(s):
When using the sampling wizard to configure an activity for remote data collection or when configuring the sampling collector, the time-based sampling option is grayed out.

Solution:
Currently, only Event-based sampling (EBS) is supported by the remote agent for Linux*. Using EBS with the Clockticks event is usually equivalent to TBS. See the online help for information regarding Non-halt and Non-sleep Clockticks for certain Pentium® processors.

Operating System:

To generate debug symbols for a Borland Delphi Enterprise Version 6.0 project:

1. Set the following in the Project/Options/Compiler/Debugging tab:
   • Debug information <ON>
   • Local symbols <ON>
   • Reference info <ON>
   • Assertions <ON>
2. Set the following in the Project/Options/Linker/EXE and DLL options tab:
   • Include TD32 debug info <ON>
3. Set the following in the Project/Options/Linker/Map file tab:
   • Off <ON>
4. Set the following in the Project/Options/Linker/Linker output tab:
   • Generate DCUs <ON>

Operating System:

• Sampling driver called sepdrv.sys is not digitally signed. x64 editions of Windows Vista* operating system disable unsigned drivers by default so that it prevents sampling collection. In order to enable the driver, reboot the system, press F8 during the boot and select Disable Driver Signature Enforcement. This setting does not persist across boot sessions.
  
  
• Installation may hang on Windows* Longhorn Server during CGExeCtrl.exe and CGExeCtrl_LINUX.exe registration. If it hangs, open Task Manager and end hanging processes CGExeCtrl.exe and CGExeCtrl_LINUX.exe and continue installation. Some call graph features may not work but the rest of features is not affected.

Operating System:

Usually VTune™ Performance Analyzer can be run on a system with any new Intel® processor and certain features such as call graph work in the same way they do on earlier processors. Other features such as sampling collection or disassembly view may give inadequate results. Please check product release notes for supported processors.