SunVTS 6.2 Patch Set 1 Release Notes

The SunVTStrademark 6.2 Patch Set 1 (PS1) software is designed for the Solaristrademark 10 6/06 operating system (OS) and is compatible with the Solaris 10 3/05 or later OS.

Note - All new features, tests, and test enhancements that are released in SunVTS 6.2 are documented in the SunVTS 6.2 Test Reference Manual, and SunVTS 6.2 User's Guide. These documents are included on the Solaris on Sun Hardware collection on the Solaris Documentation DVD, in the extra value (EV) directory. These documents are also available at:

For the latest version of this document (819-7446), go to:

Note - The Netra-CT 820 DMC Test (dmctest) will be discontinued in a future release of SunVTS.

Note - The Automatic Configuration feature in the SunVTS GUI that automatically assigns predetermined sets of test options will be discontinued in a future release of SunVTS.

SunVTS Support for the Solaris OS on x86-Based Systems

Note - In this document these x86 related terms mean the following:
"x86" refers to the larger family of 64-bit and 32-bit x86 compatible products.
"x64" points out specific 64-bit information about AMD64 or EM64T systems.

Starting with the Solaris 10 OS, the SunVTS infrastructure and core diagnostics are available for x86 platforms. Starting with Solaris 10 3/05 HW1, SunVTS diagnostics for x86 platforms are supported in the AMD 64-bit environment for the SunVTS kernel (vtsk). All diagnostics except the System Test (systest) are ported to 64-bit.

SunVTS is supported and tested on the following Sun x86 platforms:

Note - If you perform SunVTS on an unsupported platform, a warning message appears and SunVTS stops.

You must install the x86 version of the SunVTS packages to perform SunVTS on x86 platforms. The software packages use the same names as in the SPARC® environment. The SunVTS packages delivered separately for both x86 and SPARC Solaris platforms are as follows:

The SunVTS components available for x86 Solaris platforms are as follows.


SunVTS tests:

Displaying SunVTS Package and Version Information

Use the following command to display SunVTS package information:

# pkginfo -c SUNWvts SUNWvtsr SUNWvtsts SUNWvtsmn

You can also use either of the following commands to display additional SunVTS package information:



Use either of the following commands to display SunVTS version information:

Open Issues

Possible Installation Issue:
Install and Uninstall Using the Same Program

Use the same tool or utility for installation and removal of the SunVTS software. If you use pkgadd for installation, use pkgrm to uninstall; if you use Web Start for installation, use the Product Registry to uninstall.

Possible Runtime Issues for Both x86 and SPARC Platforms

CR 6353136 qlctest Prevents Multiple Test Instances

qlctest opens an exlusive path to the adapter port. This causes other instances of qlctest to fail when run on any port on the same board as a port that is already being tested.

Workaround: None.

CR 6390537 SunVTS TTY Interface (vtstty) Could Core Dump

Starting the TTY interface with the vtstty command without typing ./vtstty could cause a core dump when log information is displayed.

Workaround: Type ./vtstty when starting the SunVTS TTY interface.

CR 6424220 netlbtest External Loopback Core Dump

Using the netlbtest external loopback test could cause a core dump.

Workaround: None.

CR 6423074 SunVTS Kernel Could Cause a Core Dump

The SunVTS kernel (vtsk) could cause a core dump due to a SIGBUS call during a kernel routine, either when tests are forked or when tests exit. If this occurs, an error message similar to the following is displayed:

"Not connected to any SunVTS kernel"

Workaround: Start tests with just "Start" instead of using session record mode ("Start with Record").

CR 6365751 Blank Dialog Boxes Displayed From the installer Utility When Installing SunVTS from the Solaris 10 1/06 SPARC and x86 CD-ROMs

When launching the installer utility on the Solaris 10 1/06 CD-ROMs, the pop-up dialog box displays two choices: Typical and Custom. If Typical is selected, the next dialog box, "The following items will be installed," is blank. This issue does not occur on the Solaris 10 1/06 DVD.

Workaround: None.

CR 6331819 SunVTS Memory or CPU Tests Could Fail Due to Lack of System Resources

When too many instances of SunVTS functional tests are run in parallel on UltraSPARC® T1 CMT CPU-based (sun4v) entry-level servers with low memory configurations, SunVTS tests might fail due to lack of system resources. For example, you could see an error message similar to the following:

"System call fork failed; Resource temporarily unavailable"

Workaround: Decrease the number of SunVTS test instances or perform SunVTS functional tests separately. In addition, you can increase the delay value for CPU tests or increase the test memory reserve space.

CR 6310384 Using usbtest

The usbtest keyboard test might indicate a successful keyboard probe when a keyboard is not present.

Workaround: None.

CR 6349218 Using netlbtest on Sun Fire T2000 Servers

Performing netlbtest on all ipge ports simultaneously in systems with Sun PCI-Express Dual Gigabit MMF/UTP adapters could fail. Performing netlbtest on one port per adapter, avoids this failure.

Workaround: Perform netlbtest on one port per Sun PCI-Express Dual Gigabit MMF/UTP adapter.

CR 6306254 Using qlctest

On dual-port host bus adapters (HBAs), testing both ports simultaneously could cause intermittent test failures.

Workaround: Test only one port of dual-port HBAs at a time.

CR 6345990 Creating Option Files on Enterprise Servers

Creating option files on Sun Enterprisetrademark and Sun Fire 15K servers (UltraSPARC III) with the SunVTS GUI could cause a core dump.

Workaround: Use the TTY user interface to create option files.

CR 6344791 Supporting x86 Clients on a SPARC Server

Installing SunVTS x86 packages on a SPARC server to serve x86 clients with SunVTS images is not supported. Installing SunVTS SPARC packages on an x64 or x86 server to serve SPARC clients is supported.

Workaround: None.

CR 6333687 Using cddvdrwtest

In rare cases, repeated reuse of DVD+RW optical media on Sun Ultra 45 workstations could cause failures when performing high stress DVD+RW SunVTS tests.

Workaround: Replace the DVD+RW media upon failure, or use other types of media such as CD-RW.

CR 6220163 Using cddvdtest

cddvdtest might fail when used for testing CD/DVD RW drives with Read/Write media.

Workaround: Either use a blank media for testing, or insert a CD-ROM media into the drive and restart SunVTS. The user interface then invokes the test with read only options.

CR 4858028 Using serialtest and disktest Simultaneously

Sun Bladetrademark 100 and 150 systems with SunVTS can produce errors when the serial port controller (southbridge) is also handling other traffic as data access from and to the IDE hard disk. With SunVTS simultaneously running serialtest and disktest on Sun Blade 100 and 150 systems, you might see serialtest report failures.

Workaround: Do not perform serialtest and disktest simultaneously.

SunVTS Does Not Support Processor Sets

If processor sets are defined, you must first delete the processor sets before running SunVTS.

Workaround: None.

Netra CT 820 Server Support

The Netratrademark CT 820 server is not currently supported in Solaris 9 or Solaris 10 Operating Systems.

Possible Runtime Issues for x86 Platforms

bmcenvironment Test Displays Failure When Critical Threshold is Reached but Not Exceeded (CRs 6328901, 6363524, 6368948, and 6368997)

On Sun Fire V20z and Sun Fire V40z servers, it is possible for some sensor readings to reach the corresponding critical threshold without exceeding it. The bmcenvironment test flags a sensor reading as a failure both when the critical threshold is reached and exceeded. If a failure occurs due to a sensor reading reaching but not exceeding the critical threshold value, as shown in the log, the failure can be disregarded.

Workaround: None.

CR 6344143 Using qlctest

Performing qlctest with the default settings (Exclusive test mode and Online Selftest enabled) could fail with an error message similar to the following:

    (1)wrong/missing QLC driver
    (2)system software
    (1)Reload correct revision driver
    (2)if the problem persists, contact authorized Sun service provider

Workaround: Disable the Online Selftest.

Possible Runtime Issues for SPARC Platforms

Using env5test (CR ID 6176527) and i2ctest (CR ID 6176554)

env5test and i2ctest could fail due to a Solaris 10 OS PICL initialization issue. When PICL is stopped and started, the tests pass appropriately.

Workaround: Enter the following commands directly after the Solaris OS is booted:

# cvsadm disable /system/picl
# cvsadm enable /system/picl

CR 4938281 pfbtest Fails When Used in the Gnome Desktop Environment

pfbtest might fail when performed in the Gnome desktop environment on a Sun XVR-100 graphics accelerator if the test is performed in the default console window.

This failure does not occur in the Solaris 8 2/02 OS and the Solaris 8 HW 3/03 OS. If this failure occurs, an error message similar to the following is displayed:

pfb3(pfbtest)            passes: 26 errors: 12

Workaround: Most graphics tests fail when running under Gnome. Enter the xscreensaver-command -exit command before performing graphics test under the Gnome desktop environment to avoid these failures.