How to run DTRACE tests on VM environment

Owned by Vitaly Shaburov
Last updated: Apr 12, 2024
3 min read

1. Setup VM with:

  • CPU - 4

  • Memory - 8GB

  • Hard disk - 100GB

  • Have to use DEBUG build, where we have debug macro

Setup process is described in this instruction.

Note : If you already created dilos_BASE BE according the instruction, and there is no any new tested stable version, just execute the following command:

beadm activate dilos_BASE

In other case if you have already the dilos_ISO_orig BE - make the command:

beadm activate dilos_ISO_orig

Then reboot and start the instruction from the section Step 6. Prepare VM for Tests Running:

reboot

If you have no one of these 2 BEs then start the instruction from the beginning.

Note : Create ztest user if you forgot to do it according the instruction:

sudo useradd -m -d /var/ztest -g staff -s /bin/bash ztest

sudo passwd ztest

echo "ztest ALL=(ALL:ALL) NOPASSWD: ALL" >> /etc/sudoers.d/ztest

2. Install packages for DTRACE tests:

Note : If you already did it on the previous step when preparing VM to run, then you can skip this step and go to the next one.

sudo apt update reboot sudo apt install system-dtrace-tests build-essential oracle-java8-jdk perl testrunner python3 bc

DTRACE tests take about 90 minutes or more for execution. So, there is a way how to run tests and to turn off the computer with further connection to your running tests. For this you have 2 conditions:

You can install this utility here with the following command:

sudo apt install screen

3. Login by user ztest and run tests:

sudo /opt/SUNWdtrt/bin/dtest -d /var/tmp

Wait for about 90 minutes.
Fault logs will be saved at:

/var/tmp/test_results/<ISO TIME>

If you are connected by SSH and would like to turn off SSH session or even temporary turn off your computer, then you have enter the following command for tests running:

Then you can in any time press Ctrl-A d and after that close your SSH session.

When you would like to get back, login again to SSH please and enter the command:

and you will be back to your running tests.

Fault logs will be saved at: