LoadGen Server Stress - Start Test for Server
This automated test measures the stress load on a server. This test does the following:
Copies test files to the Master Client.
Runs the test on the Master Client.
Copies the test logs after the test finishes.
Test details
Area | Description |
---|---|
Specifications |
|
Platforms |
|
Supported Releases |
|
Expected run time (in minutes) | 1440 |
Category | Scenario |
Timeout (in minutes) | 86400 |
Requires reboot | false |
Requires special configuration | false |
Type | automatic |
Additional documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):
Running the test
LoadGen test can be used to stress a Windows Server system. This server could be a physical server or a virtual machine. If physical server has more than 64 logical processors or has more than 1 TB memory, LoadGen should run against the physical server directly. Otherwise, follow the steps below to create a Hyper-V virtual machine as the LoadGen stress target.
- On the System Under Stress (SUT), install the Windows Server operating system version which is to be tested, and install the Hyper-V role.
- Create a Windows Server 2016 virtual machine for the version of Windows Server which is to be tested, with the maximum allowed logical processors, memory, network, and storage that the SUT can support.
- This virtual machine needs to join to the test domain and have the s HLK client installed.
Run the following job to prepare the virtual machine:
- Open HLK Manager.
- In the Explorers menu, click Job Monitor.
- In Job Explorer, press CTRL+Q to open the query pane, and search for jobs where Name Equals LoadGen Config SUT.
- In the Results pane, note the Job ID for the matching job.
- In the Explorers menu, click Job Monitor.
- In Job Monitor, navigate to the machine pool that contains the SUT, MC, SCs, and virtual machine, and highlight the virtual machine.
- Right-click the machine selection and click Schedule by Job ID.
- In the prompt area, enter the Job ID from step 4, and then click OK.
- In the Schedule Jobs window, enter the Domain name, user name, and password of the account that will be used to run test. This account should be a domain account and have administrative privileges on the SUT, MC, SC, and virtual machine.
- In the toolbar, click Create Schedule.
- Wait for the job to run and the selected machine to return to the Ready state.
Before you run the test:
Verify the test setup as described in the test requirements: System Server Testing Prerequisites and Test Server Configuration.
Run LoadGen Server Stress - Run First - Set Machine Policies first, to setup the correct machine policy settings.
From Windows Hardware Lab Kit (Windows HLK) Studio, select and run the test:
- Navigate to the Tests tab.
- Select LoadGen Server Stress - Start Test for Server.
- Click the Run Selected link.
- In the Schedule dialog, enter parameters, and map machines to roles:
- If a Hyper-V virtual machine is created, enter the name of virtual machine as StressTarget. Otherwise, use the default value which is [SUT].
- Use the Role dropdown to select machine for the MC role (SUT will be prepopulated).
- Click OK to schedule the test.
Troubleshooting
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.
Review Server log file (srvlog.xml) for errors. Search for "error" entries. If you receive the following error for Windows Server 2008 R2:
Main::RunMain:: Test Check Spsrv stopped and did not pass required pass percentage (100) (Error=0x80004005)
Close Windows HLK Studio. Change the system under test (SUT) computer name to 14 characters or less. Reboot the SUT. Open Windows HLK Studio and re-run this test.
If you receive the following error for Windows Server 2012 R2 or later:
Main::RunMain:: Test Check Spsrv stopped and did not pass required pass percentage (100) (Error=0x80004005)
Close Windows HLK Studio. Change the SUT computer name to 15 characters or less. Reboot the SUT. Open Windows HLK Studio and re-run this test.
For additional troubleshooting information, see Troubleshooting System Server Testing.
More information
Parameters
Parameter name | Parameter description |
---|---|
KitTestBinRoot | |
FolderToCopy | |
KitName | |
WDKLogo | |
ExtraParams | |
KitOSBinRoot | |
StressTarget | If certify a physical system running Hyper-V, enter the name of the VM running on that physical system. Otherwise, don't change the default value. |