HP SVA V2.1 System Administration Guide

sva_ovp(8)
NAME
sva_ovp -- Verifies that the components of an SVA system are working properly.
Synopsis
sva_ovp { -d display-surface,... } [ -g geometry ,...] [ -i display ] [ -l ] [ -h ]
Options
-d display-surface or
--display-surface name
Specifies the list of Display Surfaces to test. It defaults to
the first supported display resolution.
-g geometry or
--tile_geometry geometry
Specifies the tile geometries (resolutions) to test. Must be
one or more of the tile geometries supported on the cluster.
It defaults to 1280x1024.
-i display or
--input_display display
The X server where the DMX console displays. It defaults
to the X display on the cluster head node.
-l or --long-runtime
On each specified Display Surface, the OVP runs for 10,000
frames, rather than the default of ten frames. This is useful
when trying to determine if a given Display Surface is
configured properly.
-h or --help
Prints usage information.
Description
Users Supply Chain, Delivery, Field Service, System Administrator.
Runs On Head node.
Mode Non-exclusive.
Subsystems Tested Directly: Job launching, Display surfaces, Chromium, DMX.•
• Indirectly: Interconnect.
This utility tests the functionality of the SVA to demonstrate that a few of the core components
(job launching, Display Surfaces, Chromium) are working properly.
A short-lived 3-D application runs on all of the Display Surfaces defined on the cluster. The OVP
then verifies that the final generated frame matches the reference image for that resolution
generated at HP.
You can use the OVP in two ways:
• Test that all of the components of SVA system are working properly.
• Verify that a Display Surface is properly configured. (Internal SVA layout matches the
physical layout.)
Error Reporting
Most status information is sent to stdout, including a summary of the test results at the end of
the OVP run.
Information about individual job components is stored in
/hptc_cluster/sva/ovp/<DIRECTORY>, where DIRECTORY is a name based on the date
that the test runs. Information includes debugging information, and the png images that the
OVP generated.
As the tests run, status about each individual test is displayed, including the following:
60