Before you start the software, consider the following runtime issues:
System load: Before you run the software on your system, consider the added system activity created by the software and its effect on users. Depending on the mode you select, testing can add a significant load to your system, or it can be quite minimal.
Other applications: Some tests stress the system resources (such as virtual memory) to the point that other applications might not run.
System functionality: The software is a diagnostic tool. It runs only when your system is fully booted to run level 3 (multiuser level). The software will not run from single-user (maintenance mode) nor from run level 0 (monitor mode).
Superuser access: For security reasons, you must be a superuser to run the software.
Graphics tests: When running tests on frame buffers, do not run any other application or screen saver program that uses the frame buffer. Frame buffer graphic tests print test patterns on the display. This situation temporarily prevents you from working in your window environment.
Swap space: The amount of swap space required for testing varies widely with individual hardware and software configurations. If an adequate amount of swap space is not available on your system, the status column on the graphical user interface displays the message “waiting for swap space”.
Processor sets: The software is not supported on systems where processor sets have been created. The Oracle Solaris OS enables the creation and management of processor set, which allows the users to bind processes to a group of processors, rather than just a single processor [prset (1M)]. In the presence of processor sets, the tests can have undeterministic behavior.
Zones: The software is supported only in the Oracle Solaris global zone environment. It is not supported in local zones. The zones facility in the Oracle Solaris OS provides an isolated environment for running applications [zones(5)]. If the software is started on a local zone, it will abort with an appropriate message.
Systems in a clustered configuration: When systems are configured in a cluster, do not run Oracle VTS, as system resources for testing needs might be exhausted. This could impact the ability of a system node in the cluster to respond to heartbeat communication from the other node. If you want to test the hardware for systems in a cluster, take the systems out of the cluster mode and then test them.