During uninstallation, you may see the following message:

Uninstalling EntireX DCOM component...
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
EntireX DCOM component has been successfully uninstalled

Operating System:

Solution:

After you have installed the product and are using it, if you get an error message similar to: Error: NTD is not running at the moment, please start it before using NT services, and if, after trying to restart the ntd service, you get a message asking you to create a password for "User vtunesag" followed by an error message similar to: `vtunesag:vtunesag': invalid user, please uninstall and reinstall the product. For more information on how to uninstall the product, please refer to the information in the Installation Guide (also located in the <installdir>/INSTALL.txt document).

Operating System:

Symptom(s):

If you run sampling collection on systems under the Eclipse GUI when per CPU Buffering is enabled and you get an error message: "driver ioctl failed," the sampling driver will be unusable.

Cause:

The VTune™ analyzer sampling driver currently has issues when sampling using the Eclipse GUI (vtlec) under Per CPU Buffering mode on "-sn2" and "-rtgfx" SGI ProPack4 SP3 kernels. This issue will be fixed in a subsequent release of the analyzer.

Solution:

To work-around this issue, follow these steps:

1. Exit the Eclipse IDE, and remove and reload the sampling driver.
2. Go to <install dir>/vdk and run rmmod-vtune to remove the driver.
3. Then, from the same directory, run insmod-vtune to install the sampling driver again.

If you don't mind reloading the driver before every collection, you can use the Eclipse GUI. Otherwise, you can collect sampling data in Per CPU buffering mode via the command line interface and view and analyze the results using the Eclipse GUI.

If you do not need the Per CPU Buffering capability, you may disable it by setting SEP_PERCPU_BUFFER=0 and you will be able to use the Eclipse GUI without a problem.

Symptom(s):

Usually above problems appear when collected Call Graph data size is big (200Mb and more). VTune™ analyzer has several mechanisms to control the amount of collected Call Graph data: Pause/Resume functionality, Pause/Resume API calls, and Call Graph collector configuration options.

Solution:

The simplest way to manage the size of data is using of Pause/Resume functionality. It is available from the GUI or using the command line ActivityController utility. If you are not able to estimate visually the moment to pause/resume data collection, then you can use calls to VTune Pause/Resume API functions to manage data collection from inside your code. Several collector configuration options also allow you to reduce the size of collected data. You can change instrumentation level for modules and disable instrumentation of most insignificant functions using " function selection" collector configuration option.

There is another method to reduce the amount of displayed Call Graph data - Call Graph Pruning. Using it you can filter out functions with small contribution to execution throughput and leave functions which are the main contributors (Linux only).

Call Graph pruning is supported in Eclipse GUI and vtl command line interface. It is not supported by standalone viewer (vtl view -gui).

To use pruning in Eclipse GUI go to Window » Preferences » VTune(TM) » Call Graph » Function Filtering.

To use pruning in command line use the following commands:

#vtl view -pr 90
#vtl view -functions -pr 70
#vtl view -calls -pr 80
#vtl view -critical-path -pr 90

Where -pr option shows that Call Graph results must be filtered to show the most time-contributed functions with 70-90% execution time coverage. To see the effect you can compare the size of files "#vtl view > out1" and "#vtl view -pr 70 > out2" for your collected Call Graph data.

When unpacking a pack-and-go file created by the VTune™ Performance Analyzer 8.0 for Linux*, using the VTune Performance Analyzer 7.2 on Microsoft* Windows*, you may receive the following errors in the Output window:

No jit files in this project.
The unpack process failed.

The problem occurs when unpacking call graph results. That is, packing of sampling results in version 8.0 and unpacking in version 7.2 is supported, as long as you select Uncompressed in the Pack and Go dialog of version 8.0.

Note: This known issue was resolved in versions 9.0 of the VTune Performance Analyzer for Windows* and for Linux*.

Operating System: