SUSE Yes Certification Kit

SUSE Yes Certification Test Kit
7.7 www.SUSE.com
October 12, 2017 SYSTEM TEST TOOLS FOR SUSE®

LINUX
novdocx (en) 6 April 2007
Legal Notices
SUSE LLC., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, SUSE LLC., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, SUSE LLC., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE LLC.,
reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify
any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. Export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please
refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software. SUSE assumes no
responsibility for your failure to obtain any necessary export approvals.
All files provided in this release are subject to the Novell Developer License Agreement, which can be found in the
license.txt file provided in the System Certification Test Kit download.
Copyright © 2004-2016 SUSE LLC. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
SUSE LLC., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent
applications in the U.S. and in other countries.
SUSE LLC.
1800 South Novell Place
Provo, Utah, 84606
U.S.A.
www.SUSE.com
Online Documentation: To access the online documentation for this and other Novell products or SUSE products, and
to get updates, see www.novell.com/documentation or see www.suse.com/documentation.
Online SUSE Developer Services Program Guide Documentation: To access the online SUSE Developer Services
Program Guide, see https://www.suse.com/docrep/documents/h4mylk7uec/suse_developer_services_pg.pdf .
2
Novell Trademarks
For a list of Novell trademarks, see Trademarks (http://www.novell.com/company/legal/trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
3
4
Contents
About This Guide.............................................................................................................................11
Certification Policies and Process....................................................................................................12
1.1 Introduction.........................................................................................................................12
1.2 Certification Policies Location...........................................................................................12
1.3 New Companies and New User Access..............................................................................12
1.4 Certification Process Overview..........................................................................................12
1.5 Test Results and Audits.......................................................................................................13
1.6 Support Information / URL Addresses...............................................................................13
1.7 Company Testing Lab.........................................................................................................14
1.8 Lab Site Inspection.............................................................................................................14
Linux Test Suite ...............................................................................................................................15
2.1 Configuring the Hardware..................................................................................................15

2.2 Setting Up TC.....................................................................................................................19
2.2.1 Installing SLES 11 SP4 on TC.........................................................................................19
2.2.2 Installing the Test Kit on TC............................................................................................24
2.2.3 Setting Up the DHCP/PXE Server on TC.......................................................................25
2.2.4 Adding ISO Images to the PXE Menu on TC..................................................................26
2.2.5 Configuring the SUT For and Using the PXE Boot........................................................26
2.3 Setting Up SUT...................................................................................................................28
2.3.1 Installing SLE on SUT Through PXE.............................................................................28
2.4 Installing the Test Kit on the SUT .....................................................................................29
2.5 Updating the Products.txt File............................................................................................32
2.5.1 Updating by Internet........................................................................................................32
2.5.2 Updating with Other Media.............................................................................................32
2.6 Creating a New Test Project...............................................................................................34
2.7 IP Address Information.......................................................................................................35
2.8 Xen Virtual Machine Tests Setup.......................................................................................37
2.9 Validate Install Test.............................................................................................................38
2.10 Component Check Test.....................................................................................................39
2.11 Product and Report Information Entry.............................................................................39
2.11.1 System Information Entry..............................................................................................40
2.11.2 Company Information ...................................................................................................44
2.11.3 Ports and Bus Information.............................................................................................45
2.11.4 Video, LAN, HBA and Storage Device Information...................................................48
2.11.5 Saving the Test Project...................................................................................................61
2.12 Test Results Definitions....................................................................................................62
2.13 Memory Persistence Test.................................................................................................62
2.14 Kdump Test.......................................................................................................................62
5
2.15 Serial Port Test Setup........................................................................................................63
2.16 Video Test.........................................................................................................................63
2.17 Touchscreen Test...............................................................................................................63
2.18 Speaker Test......................................................................................................................64
2.19 Microphone Test...............................................................................................................64
2.20 Volume Keys Test.............................................................................................................64
2.21 External Mouse Test.........................................................................................................65
2.22 External Keyboard Test....................................................................................................65
2.23 External Monitor Test.......................................................................................................65
2.24 Battery Test.......................................................................................................................66
2.25 Power Management Tests.................................................................................................66
2.25.1 Hibernate Test................................................................................................................66
2.25.2 Sleep Test.......................................................................................................................66
2.25.3 CPU Frequency Test......................................................................................................67
2.25.4 Fan Thermal Test...........................................................................................................67
2.25.5 Throttling Test................................................................................................................67
2.25.6 Brightness Test...............................................................................................................67
2.25.7 Brightness Keys Test.....................................................................................................68
2.25.8 Lid Close Test................................................................................................................68
2.26 Verify Setup Tests.............................................................................................................69
2.26.1 Verify Setup - NIC 1......................................................................................................69
2.26.2 Verify Setup - NIC 2 through 16 ...................................................................................69
2.26.3 Verify Setup – Wireless NIC .........................................................................................70
2.26.4 Verify Time Sync Setup.................................................................................................71
2.27 Specialty Tests..................................................................................................................72
2.27.1 NIC 1 Reduced Test.......................................................................................................72
2.27.2 Verify PCI Pass-Through/SR-IOV Setup .....................................................................72
2.27.3 CPU Over-Commit Setup .............................................................................................73
2.28 Optical Device Tests Overview........................................................................................74
2.28.1 Optical Verify/Write Test...............................................................................................75
2.29 Stress Tests.......................................................................................................................75
2.29.1 Persistent Memory Test.................................................................................................75
2.29.2 Memory/CPU Test Setup...............................................................................................75
2.29.3 Hard Disk/RAID Test Setup..........................................................................................75
2.29.4 NIC Test.........................................................................................................................76
2.29.5 Time Sync Test Setup....................................................................................................76
2.29.6 Floppy Test Setup..........................................................................................................76
2.29.7 Optical Read Test ..........................................................................................................76
2.29.8 USB Test Setup..............................................................................................................77
2.29.9 FireWire Test Setup.......................................................................................................78
2.29.10 Error Check Test..........................................................................................................79
2.29.11 Starting the Stress Tests...............................................................................................79
2.30 Verify Stress Tests.............................................................................................................80
2.31 Evaluating the Results of the Stress Tests........................................................................80
2.32 Post-Testing Cleanup........................................................................................................80
2.33 Get Test Logs Test............................................................................................................80
2.34 Creating the Bulletin Submission File..............................................................................81
6
Manually Installing SLED 12 ..........................................................................................................83
3.1 Configuring the Hardware for SLED 12 SP3 Testing........................................................83

3.2 Setting Up TestConsole......................................................................................................84
3.3 Manually Installing SLED 12 SP3 on SUT........................................................................84
3.4 Manually Installing the Test Kit on the SLED 12 SP3 SUT ..............................................87
3.5 Starting the Tests.................................................................................................................88
Xen Virtual Machine Tests...............................................................................................................89
4.1a Installing a Xen Virtual Machine......................................................................................92

4.1b Installing a Xen Virtual Machine......................................................................................94
4.1c Automated Installation of a Xen Virtual Machine............................................................98
4.2 Using SLES Virtual Machines – Help Section...................................................................98
4.3 Manually Installing the Test Kit on the SLES Xen Virtual Machine.................................99
4.4 Configuring Xen for Network PCI Pass-Through ...........................................................100
4.5 Configuring XEN for SR-IOV .........................................................................................102
4.6 Installing a Windows 2008 or 2012 Virtual Machine.......................................................105
4.7 Installing the Test Kit on the Windows Virtual Machine..................................................106
4.8 Preparation For Quick Install Of Virtual Machines..........................................................108
4.9 Quick Install Of Virtual Machines....................................................................................108
Kernel-based Virtual Machine Tests...............................................................................................110
5.1 Configuring the KVM server............................................................................................110

5.2 Installing a Kernel-based Virtual Machine.......................................................................111
5.2b Installing a KVM Virtual Machine with SLES 12 SP3 VM wizard...............................114
5.2c Automated Installation of a KVM Virtual Machine........................................................115
5.3 Installing a Windows 2008, 2008 R2, or 2012 Kernel Virtual Machine...........................115
5.4 Installing the Test Kit on the Windows Virtual Machine..................................................116
5.5 Configuring KVM for Network PCI Pass-Through ........................................................118
5.6 Configuring KVM for SR-IOV ........................................................................................120
5.7 Manually Installing the Test Kit on the SLES KVM Guests............................................124
5.8 Starting the Tests...............................................................................................................125
Manually Installing SLES 12 or SLES 11 .....................................................................................126
6.1 Manually Installing SLES 12 SP3 on SUT.......................................................................126

6.2 Manually Installing the Test Kit on the SLES 12 SP3 SUT ............................................128
6.3 Manually Installing SLES 11 SP4 on SUT.......................................................................129
6.4 Manually Installing the Test Kit on the SLES 11 SP4 SUT ............................................134
6.5 Starting the Tests...............................................................................................................135
Troubleshooting and Help .............................................................................................................136
A.1 Installation Issues.............................................................................................................136
7
A.1.1 Removing the ELIO Boot Tables..................................................................................136
A.2 Installing SLES On TC....................................................................................................138
A.2.1 TC Connection..............................................................................................................138
A.2.2 Configuring IP Addresses without Yast........................................................................138
A.2.3 Installing The Missing rpm's.........................................................................................138
A.2.4 Installing The Test Kit Manually On The SLES Xen VM ...........................................139
A.3 TestConsole......................................................................................................................139
A.3.1 TestConsole displays Error Attempting to Run Test.....................................................139
A.3.2 TestConsole Locks Up or has Blank Screen during Testing ........................................140
A.4 Time Synchronization Issues...........................................................................................140
A.4.1 Checking the Time Synchronization Configuration.....................................................140
A.4.2 Time Sync Test Fails or Time Sync Verify Test Fails...................................................140
A.5 Component Check Issues.................................................................................................141
A.6 Validate Install Test, Component Check, and Get Test Logs...........................................141
A.7 Get Test Logs Test............................................................................................................142
A.7.1 Test Logs Location........................................................................................................142
A.7.2 Failure to Gather the Test Logs.....................................................................................142
A.8 Video and Desktop Effects Testing Issues.......................................................................143
A.8.1 Video Test Issues...........................................................................................................143
A.9 Serial Port Test.................................................................................................................143
A.9.1 Serial Port Test Fails.....................................................................................................143
A.9.2 Checking the Serial Port functionality..........................................................................144
A.9.3 Serial Port Debugging with Minicom...........................................................................145
A.10 Stress Tests.....................................................................................................................146
A.10.1 NIC Issues...................................................................................................................146
A.11 Test Kit Installation Issues.............................................................................................147
A.12 General Issues................................................................................................................148
A.12.1 System Hang After Reboot.........................................................................................148
A.12.2 Tests Run More Than 12 Hours.................................................................................148
A.12.3 USB Tests Fail...........................................................................................................150
A.12.4 Multiple Test Projects on TC.....................................................................................150
A.13 Testing issues on SUT ...................................................................................................151
A.13.1 Tests will not start on SUT.........................................................................................151
A.14 PXE Install Issues..........................................................................................................151
A.15 KVM Issues...................................................................................................................151
A.15.1 KVM GUI Not Responding .......................................................................................151
A.15.2 KVM Time issues ......................................................................................................152
A.15.3 KVM GUEST Time is not in sync with Host ............................................................152
A.16 Xen Issues......................................................................................................................152
A.16.1 Xen GUEST Time is not in sync with Host ...............................................................152
A.17 Kdump Issues.................................................................................................................153
A.17.1 Changing the Kdump Settings....................................................................................153
A.17.2 Manually Starting the Kdump.....................................................................................154
A.17.3 IP Address Issues with Kdump...................................................................................154
A.18 Product and Report Information Entry Issues................................................................155
A.18.1 Product and Report Information - Missing Device.....................................................155
A.19 PCI Pass-Through Issues...............................................................................................155
8
A.19.1 PCI Pass-Through – VM Fails to Start......................................................................155
A.20 IPv6 Information...........................................................................................................156
A.20.1 IPv6 Address Generation...........................................................................................156
A.21 Hibernate Test Issues.....................................................................................................156
A.21.1 Hibernate Test PASS w/WARNING...........................................................................156
A.22 Sleep Testing Issues.......................................................................................................157
A.22.1 Sleep Test PASS w/WARNING..................................................................................157
A.23 USB Virtualization Pass Through Setup........................................................................157
Uninstalling the Test Kit from a Linux System .............................................................................158
Using TestConsole..........................................................................................................................160
C.1 Introduction......................................................................................................................160
C.2 Project Contents...............................................................................................................160
C.2.1 Starting Tests.................................................................................................................160
C.2.2 Selecting and De-selecting Tests...................................................................................160
C.3 Run Queue........................................................................................................................161
C.4 Project Log.......................................................................................................................161
C.5 TestConsole Testing Modes..............................................................................................161
C.5.1 Debug Mode..................................................................................................................161
C.5.2 Loop Mode....................................................................................................................161
C.6 Importing Product Information from an Existing Project................................................162
C.7 TestConsole Error Messages............................................................................................163
C.7.1 TestConsole Warning Messages....................................................................................163
Adding Drivers to the SUT............................................................................................................164
D.1 Introduction......................................................................................................................164
D.2 Using kISOs.....................................................................................................................165
Identifying Vendor Device Ids .......................................................................................................167
SBS Users Guide...........................................................................................................................168
F.1 Creating a Bulletin in SBS using a Bulletin Submission File ..........................................168

F.2 Open State - Partner should do the following:..................................................................170
F.3 Needs Response State - Partner should do the following:................................................174
F.4 Final Customer Review State - Partner should do the following:....................................174
F.5 Proposing a Component in SBS........................................................................................175
F.6 Configuration Notes .........................................................................................................176
F.7 Proposing a Driver for a Component in SBS....................................................................178
F.8 Process for Creating a 3C Bulletin...................................................................................179
F.9 Process for Creating a SBS user account .........................................................................180
9
F.10 Process for adding a new Company to SBS ..................................................................180
Third Party Hypervisor Testing......................................................................................................181
Downloading SLE Products and Patches.......................................................................................183
ARM Certification .........................................................................................................................185
Revision History.............................................................................................................................186
10
About This Guide
The System Test Tools for SUSE® Linux contains a procedure manual and all test tools necessary to test the SUSE®
products used in the SUSE Yes Certified™ system certification process. The manual explains how to install the
software and set up hardware and software configurations.
Audience
This manual is intended for users who have experience with computers, networking, Linux, and Microsoft Windows.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation included with this
product. Please use the User Comments feature at the bottom of each page of the online documentation.
Documentation Updates
For the most recent version of the System Test Tools and documentation, visit System Test Tools for SUSE LINUX
(https://www.suse.com/partners/ihv/yes/system-test-tools-for-suse-linux.html).
Additional Documentation
For more documentation on YES Certification, see:
• SUSE YES CERTIFIED Program (https://www.suse.com/partners/ihv/yes/)
• YES certifying hardware (https://www.suse.com/partners/ihv/yes/)
• Developer information (https://www.novell.com/developer/)
Documentation Conventions
In SUSE documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-
reference path.
A trademark symbol (®, ™, etc.) denotes a SUSE trademark. An asterisk (*) denotes a third-party trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the
pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux or UNIX,
should use forward slashes as required by your software.
11 About This Guide

1
Certification Policies and Process
1.1 Introduction
SUSE designed this Test Kit to aid computer system vendors in the process of testing their own computer systems.
This Test Kit provides partners with the means to set up and maintain labs capable of performing SUSE compatibility
testing on their computer systems.
SUSE designed the tests contained in this Test Kit to verify hardware compatibility between systems and SUSE
products. This Test Kit contains written instructions and test tools for evaluating compatibility. SUSE highly
encourages hardware vendors to use these tools during all phases of their hardware development, not just the final
testing phase.
The certification testing is intended to test a system and all of it's components. All of the onboard components are
required to be tested. The best approach is to test the system in it's most capable marketed configuration. A system
that is sold in multiple configurations should be tested with the maximum and the most extensive configuration
possible. The most capable configuration will most likely take advantage of all components in the system. Also a
most capable certified system can be used to create 3C bulletins which can represent a less capable configuration.
1.2 Certification Policies Location

The Yes Certified System Test Kit Policy document can be viewed at:
https://www.suse.com/partners/ihv/pdf/System_Certification_Policies.pdf
1.3 New Companies and New User Access

We use a database called SUSE Bulletin System (SBS) to create the Yes Certification Bulletins. New Companies will
need to provide their complete address and other information in order to be added to our SUSE Bulletin System (SBS)
database. To have your company added to SBS, please read and follow the process for adding a new company to
SBS in section F of this documentation.
Access to the SBS database is needed to create and release Yes Certification bulletins. New users will need to create
an account in order to access SBS. To create a new user account please read and follow the process for creating a
SBS user account in section F of this documentation.
1.4 Certification Process Overview

1 Ensure that you have the latest System Test Tools and documentation. The latest System Test Tools and
documentation can be downloaded from:
https://www.suse.com/partners/ihv/yes/system-test-tools-for-suse-linux.html.
12 Certification Policies and Process

2 Install the OS and Test Kit onto the Testconsole (TC) system.
3 Install the OS and Test Kit onto the System under test (SUT).
4 On TC create a testing project for the System Under Test (SUT).
5 On TC enter hardware component information about your SUT.
6 Perform the tests individually in the order (top to bottom) displayed in the test project contents window. The stress
tests must be started together at the same time.
7 Review the SUT project test results.
8 Report any changes to the product information to your assigned engineer (DS250 and above only).
9 Be aware that changing SUT System or CPU information in TestConsole after testing will reset the test results.
10 Generate the the bulletin submission (.zip) file then upload it into SBS.
11 In SBS review the bulletin submission then submit the bulletin for review.
12 SUSE will review the test report and process the bulletin submission. All communications about the bulletin will
be done in the bulletin communications section of SBS, not through email.
13 Once all issues are resolved, SUSE will submit your bulletin to final customer review.
14 You will release the Yes Certification Bulletin. The Yes Certification Bulletins are publicly published and can be
found at the YES CERTIFIED Bulletin Search site located at https://www.suse.com/yessearch/Search.jsp
1.5 Test Results and Audits

SUSE will review the test results and configuration for accuracy to insure the system meets SUSE standard's for
SUSE Yes Certification. Most tests require a minimum time for running the testing software. If the system encounters
errors after the minimum test time, SUSE reserves the right to determine pass/fail status of the system for that test.
SUSE will also perform periodic audits on submitted test results. SUSE may require the product and the test results of
that product to be shipped to SUSE in order to perform an audit. SUSE will only issue a certification bulletin after the
product passes the audit. In the event of an audit failure, SUSE will suspend authorization to perform testing. Upon
failure, SUSE will determine whether to completely revoke testing authorization or only temporarily withhold
authorization until compliance is fully met.
1.6 Support Information / URL Addresses

If there are any questions regarding the SUSE System Test Kit or Novell PartnerNet for Technology Partners
programs, please contact SUSE.
Web Resources
• YES Certified Systems Test Kit for Linux (https://www.suse.com/partners/ihv/yes/system-test-tools-for-suse-

linux.html)
• SUSE home website (https://www.suse.com/)
• YES Certified Bulletin Search (https://www.suse.com/yessearch/Search.jsp)

1.7 Company Testing Lab
All partner level participants must set up a test facility at their company for the purpose of performing system
certification testing. The test lab must have a minimum of the following:
• Current copy of the System Test Kit

• Windows 2008 Server with latest service pack
• Windows 2012 Server with latest service pack
• SUSE LINUX Enterprise Server 11 SP4 64 bit (Must be downloaded from the SUSE website)
• SUSE LINUX Enterprise Server 11/12 with the latest service pack (must be downloaded from the SUSE
website)
• SUSE LINUX Enterprise Desktop (SLED) 12 with the latest service pack (must be downloaded from the
SUSE website)
1.8 Lab Site Inspection

SUSE reserves the right to perform lab inspections at each authorized self-testing lab.

2
Linux Test Suite
Use this test suite to certify systems with SLES 11/12(latest support pack), SLED 12 (latest support pack), Xen,
KVM.
2.1 Configuring the Hardware

Minimum Requirements for System Under Test (SUT)
✔ Minimum SLE requirements must be met on the SUT hardware

✔ Direct access to the system (do not use remote access, do not use SSH)
✔ 512 MB RAM plus 265 MB for each CPU core. Refer to the Xen doc section for Xen requirements. Refer
to the KVM doc section for KVM requirements.
✔ 36 GB hard drive, 120 GB hard drive for KVM and Xen testing.
✔ Null modem serial cable (Required for systems with serial ports)
✔ 2 USB hard drives (Required for systems with USB ports) or USB flash drives (min 2 GB free space), no
spaces in the volume name.
✔ 2 IEEE 1394 Firewire hard drives (Required for systems with a IEEE 1394 Firewire port).
✔ 1 eSATA hard drive (Required for systems with an eSATA port).
✔ External speakers, if the SUT has a sound card.
✔ External Microphone, if SUT has a microphone jack.
✔ SLES 12(latest SP), SLED 12(latest SP), SLES 11(latest SP).
✔ A monitor that supports the video adapter.
✔ 2 Network Interface Cards (NICs) minimal if testing SLES/Xen (all NIC ports need to be tested) or 1 NIC if
testing SLED.
✔ A CD with at least 600 MB of data, for systems with CDROM drives.

✔ A DVD with at least 3 GB of data, for systems with DVD drives.
✔ Blank media as described for optical write test.
✔ Drivers which do NOT taint the kernel (Driver in the distro will not taint the kernel). Compiling drivers for
certification is not permitted. If drivers are needed please obtain them using the SUSE SolidDriver Program.
✔ We recommend that UEFI be enabled during testing (if the SUT supports UEFI).
✔ Secure Boot is not required to be enabled during testing, it is optional. If Secure Boot is enabled during
testing then a configuration note can be added stating this. The OS installation for secure boot must be
completed manually by DVD installation.
15 Linux Test Suite

✔ All SUT hardware (RAM, Hard disk Dirves, NICs, etc) must be installed in the SUT prior to installing the
SLE OS.
Minimum Requirements for TestConsole (TC)
✔ AMD 64 or Intel EM64T server class system or equivalent 64 bit (x86_64 architecture) system.
✔ Direct access to the system (do not use remote access, do not use SSH).
✔ 512 MB RAM plus at least 256 MB per CPU core.
✔ 10 GB hard drive minimum, plus 4 GB of space for each OS image.
✔ SLES 11 for x86_64 (64-bit) with service pack 4 installed.
✔ 1 NIC or more depending on SUT (2 or more NICs for SLES), (NIC Speed must match the highest capable
speed of the SUT NIC).
✔ 1 Monitor with minimum 800x600 or better resolution.

✔ Serial Port (Required to test the SUT serial port).
✔ We recommend that UEFI be disabled on the TC during testing (if the TC hardware supports UEFI).
✔ Secure Boot is not required to be enabled during testing, it is optional. We recommend that Secure Boot is
disabled on the TC during testing.
16 Linux Test Suite

Test Configuration SLES 11/12, and SLED 12
For systems with two or more Network Interface Cards (NICs).
Figure 2-1 Configuration for the SLES tests with 16 NICs
____________________________________________________________________________________
IMPORTANT: When assigning IP addresses to the NICs, do not use the range 192.168.101.0 through
192.168.101.255. These IP addresses are used in the Serial Port test.
_____________________________________________________________________________________
Figure 2-2 Configuration for the SLES tests with 2 NICs
17 Linux Test Suite

Test Configuration for SLED 12 Testing
For systems with one NIC.
Figure 2-3 Configuration for the tests with one NIC card.
_____________________________________________________________________________________
192.168.101.255. These IP addresses are used in the Serial Port test.
_____________________________________________________________________________________
18 Linux Test Suite

2.2 Setting Up TC
TC is required to use 64 bit (AMD 64 or Intel EM64T) SLES 11 Service Pack 4 (SP4).
_____________________________________________________________________________
Note: The Network Interface cards (NIC) in TC must match the highest speed NIC in the SUT.
_____________________________________________________________________________
2.2.1 Installing SLES 11 SP4 on TC
1 Delete all existing partitions from all hard drives. Section “A.1.1 Removing the ELIO Boot Tables” has
instructions which will delete any and all existing partitions. We recommend disabling Secure Boot and UEFI on
the TC.
2 Boot the system to SUSE LINUX Enterprise Server 11 SP4 from DVD.
3 Select Installation<Enter> before the 20 second timeout expires.
4 Select the English (US) Language.
5 Select the English (US) Keyboard Layout.
6 Select I Agree to the license terms, then click Next.
7 If prompted with the media check screen click Next.
8 Select New Installation, then click Next.
9 Adjust the region and time zone to match your region and time zone.
9a Click your region in the Region pull down menu on the left side or click on your time zone in the map.
9b Click your time zone in the Time Zone pull down menu on the right side or click on your time zone in the map.
10 Set the system clock to match the time of the other systems on your rack. We require that the system clock be set to
match the time of the other systems in the test harness (TC and SUT). Having logs with time stamps set to the
same time will greatly help troubleshooting.
10a Click the Change button below and to the right of Date and Time.
10b Change the Current time and Current date to be accurate.
10c Click the Accept button.
11 Click the next button to complete the setup of the Clock and Time Zone screen.
12 Select the Physical Machine scenario, and click Next.
__________________________________________________________________
Note: The Physical Machine also applies to all Xen and KVM guest installations.
__________________________________________________________________
13 Create partition for first hard disk or RAID.
13a Select Installation Settings > Partitioning.
13b Select the hard disk or RAID that you want the OS installed on.
13c Click Next.
19 Linux Test Suite

13d The message under the drive will state that the entire hard drive will be used (if the drive is empty). Otherwise
click Use entire hard disk.
13e Click Next.
14 If prompted click Accept to return to the Installation Settings screen. This prompt might occur if the drive was not
completely cleared off before starting the OS installation.
15 Select the software you want to install on the system.
15a Select Installation Settings > Software.
15b Click Details.
15c Click on the Patterns Tab.
15d Select the software patterns. Ensure that only the following patterns are checked (all remaining patterns should
be blank or deselected):
✔ Base System
✔ 32-Bit Runtime Environment
✔ Help and Support Documentation (optional)
✔ Minimal System (Appliance)
✔ Gnome Desktop Environment
✔ X Window System
✔ File Server
✔ Print server
✔ DHCP and DNS Server
✔ C/C++ Compiler and Tools
15e Click on the Search Tab.
15f In the Search box, type mgetty, then click the Search button.
15g If unchecked, check the mgetty package for installation.
15h In the Search box, type nmap, then click the Search button.
15i If unchecked, check the nmap package for installation.
15j In the Search box, type vsftpd, then click the Search button.
15k If unchecked, check the vsftpd package for installation.
15l In the Search box, type java-1_7_1-ibm, then click the Search button.
15m If unchecked, check the java-1_7_1-ibm package for installation.
15n In the Search box, type sysstat, then click the Search button.
15o If unchecked, check the sysstat package for installation.
15p In the Search box, type unixODBC, then click the Search button.
15q If unchecked, check the unixODBC package for installation, then click Accept.
15r Click Accept in the YaST agfa-fonts window.
15s If prompted, click Continue in the Changed Packages window to accept the automatic changes.
20 Linux Test Suite

15t If prompted, click Continue in the Changed Packages window to accept the unsupported packages.
15u Click Install to start the installation.
15v Click Install in the YaST2 window to confirm the installation.
16 The file copying will begin. After package installation completes, the system will restart.
17 Set the Password for user root.
17a Type suse in both fields for the root user password.
17b Click Next.
17c Click Yes to really use the password at the Password too simple or lower case is used prompt.
17d Uncheck Change Hostname via DHCP.
17e Edit the host name (e.g., TC). The following Host names examples (No spaces allowed in the name) can be
used for the Host Name field on each correlating machine:
• TC— TestConsole
• Client— Client
• SUT— System-Under-Test
• Guest 1— XenVMGuest1 (en) 6 April 2007
• Guest 2— XenVMGuest2
• Guest 3— XenVMGuest3
17f Leave the domain name the default name or enter a domain name (e.g. suse.com).
17g Click Next at the Hostname and Domain Name window.
18 Disable the firewall by clicking on disable next to firewall is enabled. The display will change to firewall is
disabled.
19 Configure the Network.
19a Click Network Interfaces in the Network Configuration window.
19b Select the NIC. It is recommended to start with the eth0 NIC.
19c Click edit.
19d Click the Statically assigned IP Address radio button.
Below is a table displaying the TC NIC ports, associated IP addresses, and the relationship to the SUT
NIC ports. The table provides the big picture for configuring the test environment. TC must be configured
to accommodate the NIC ports in the SUT. The TC Alias IP addresses spread the load evenly across
multiple NICs in TC during the NIC tests. The table below shows the TC IP address and the correlating SUT
NIC ports. When running the ifconfig utility, the NIC ports maybe listed by eth number. We have included
the eth number in the table. TC can have up to 4 physical NICs. After the 4 physical NICs, virtual NICs can
be created by way of alias IP addresses. SUT can have up to 16 NIC ports tested. Use the following table
for IP addresses.
______________________________________________________________________________________________________
TC NIC TC IP Address Notes HUB SUT NIC SUT IP Address SUT NIC Port
______________________________________________________________________________________________________
eth0 10.1.1.2 NIC 1 1 eth0 10.1.1.1 NIC 1
eth0:TC5 10.1.5.2 Alias on NIC 1 1 eth4 10.1.5.1 NIC5
21 Linux Test Suite

eth1 10.1.2.2 NIC2 2 eth1 10.1.2.1 NIC2

eth2 10.1.3.2 NIC3 3 eth2 10.1.3.1 NIC3

eth3 10.1.4.2 NIC4 4 eth3 10.1.4.1 NIC4

____________________________________________________________________________________________
19e Enter a permanent TC IP address. Example: NIC 1 = 10.1.1.2, NIC 2 = 10.1.2.2, NIC 3 = 10.1.3.2, etc.
19f Edit the Subnet mask, if necessary. Subnet mask 255.255.255.0 should be used for all NICs.
19g Click Next to return to the Network Settings window. If prompted by a blank host question, click yes (yast2
window).
19h Repeat steps 19b-19g for each NIC.
19i Click the Overview Tab.
19j If the SUT has 5 or more NICs, configure virtual addresses (aliases) on the TC.
19j1 Based on the IP addresses in the Table below choose the appropriate IP address to configure.
19j2 Click on the appropriate NIC.
19j3 Click Edit.
19j4 Click Add.
19j5 Enter the following information:
____________________________________________________________________________________
Note: If you are using different IP addresses than those listed below, write in the actual IP address used
in the IP address column.
____________________________________________________________________________________
________________________________________________________________________________________
TC Alias Name eth number IP Address Notes
________________________________________________________________________________________
TC5 eth0 10.1.5.2 Alias on NIC 1 If the SUT has 5 NIC ports
22 Linux Test Suite

________________________________________________________________________________________
19j6 Enter 255.255.255.0 for the Netmask.

19j7 Click OK.
19j8 Repeat 19j4 - 19j7 for each additional virtual IP address needed for this TC NIC.
19j9 Click Next in the Network card setup window.
19j10 Repeat 19j1 - 19j8 for each additional virtual IP address needed for this TC NIC.
19k Click OK in the Network Settings window.
19l Click Next in the Network Configuration window.
19m If prompted click No, Skip This Test in the Test Internet Connection window, then click next.
19n Click Next to use the following configuration in the Network Services Configuration window.
20 Configure the authentication.
20a Ensure the Local (/etc/passwd) radio button in the User Authentication Method window is selected.
20b Click Next in the User Authentication Method window.
20c Click Next in New Local User window.
20d Click Yes at the warning about the Empty user login.
21 Click Next at the Release Notes window.
22 Validate that the graphics adapter is configured, then click Next at the Hardware Configuration window.
_______________________________________________
Note: Ensure the monitor type and resolution are correct.
_______________________________________________
23 Uncheck Clone this system for Autoyast.

24 If prompted, click Finish at the Installation Completed screen.
25 Remove the DVD from TC.
26 If you have an extra NIC in the TC on a non-test network then an additional file needs to be created. Do the
following:
26a Open a terminal on the TC.
26b Type mkdir -p /opt/suse/testKits/system/configs/ <Enter>.
23 Linux Test Suite

26c Type echo “<IP Address of non test network NIC >” >> /opt/suse/testKits/system/configs/do_not_test
<Enter>.
27 Reboot the TC then go to Section 2.2.2, “Installing the Test Kit on TC”.
(en) 6 April 2007
2.2.2 Installing the Test Kit on TC
1 Log in to the SLES 11 SP4 TC as root.

_______________________________
Note: The default password is suse.
_______________________________
en) 6 April 2007
2 Insert the current System Test Kit CD. The CD will automount. The file browser window can be closed.
If the SUT does not have an optical media device then a loop mount procedure can be used by following the steps
below:
2a Copy the testkit ISO file onto the SUT. It can be copied onto the desktop.
2b Create a directory which will be used for the mount point (example: /root/Desktop/sck/ ).
2c Mount the ISO image on the SUT by typing the following in a terminal window:
mount /<Path>/<Testkit file name.iso> /root/Desktop/sck/ <Enter>.
Example: mount /root/Desktop/suse-systest-7.6-GM.iso /root/Desktop/sck/ <Enter>.
2d Type the following in a terminal window: /root/Desktop/sck/sck_install.sh <Enter>. Skip to step 5 below.
3 Open a terminal by right-clicking on the desktop and selecting Open in Terminal.
4 Type /<mount point>/sck_install.sh <Enter>, Example: /media/CDROM/sck_install.sh.
5 When prompted, remove the Test Kit CD then replace it with the OS DVD which was used to installed the OS onto
the SUT. If the CD will not eject using the CD tray open button, then right click on the CD icon on the desktop
then click on eject.
6 Run the Test Kit script file as indicated in the onscreen message (example: /root/sck/sck_install.sh).
7 Choose the type of system which the Test Kit is being installed onto, then press Enter. Example: 3 <Enter> for TC.
8 When prompted enter the TC's IP address (default IP address = 10.1.1.2).
9 When prompted enter the password for the TC (default password = suse).
10 Enter the password suse <Enter> at the New SMB password (Samba) prompt. No characters or asterisks will be
displayed when typing the Samba password.
11 Enter the New SMB password, suse<Enter> again.
________________________________________________________________________________________
Note: The default user name is set to root by the Test Kit. If the password is not typed the same the message:
“Error smbconfig.sh” may be displayed.
________________________________________________________________________________________
12 If TC will be used as a DHCP and PXE server (recommended) then type Y <Enter> in response to the DHCP/PXE
server question.
13 Select the NIC with the IP address 10.1.1.2. The NIC must be on an isolated network.
14 Confirm the NIC which you have selected by answering the “use ethx, is this correct?” question by typing Y
24 Linux Test Suite

<Enter>.
15 To change the the DHCP Address range follow the steps below, otherwise type: N <enter> at the prompt.
15a At the prompt: “Do you want to change the DHCP available address range?” type: Y <enter>.
15b Complete the beginning IP address for the new range then press enter.
15c Complete the ending IP address for the new range then press enter. A message will be displayed in the
terminal window stating that the DHCP server is restarting.
16 Type N <Enter> in response to the question “Would you like to add or remove ISO's” to the PXE boot install menu
question. This will be configured later.
17 Press <Enter> to exit the Test Kit install script. If the IP address of the TC is changed after this point then the Test
Kit must be re-installed.
18 Remove the OS DVD. If the DVD will not eject using the DVD tray open button, then right click on the DVD
icon on the desktop then click on eject or unmount the ISO.
19 Set the time display.
19a Right-click on the time display in the display panel.
19b Click Preferences.
19c Select 12 hour format below the words Clock Format.
19d Select Show Seconds.
19e Click Close.
_______________________________________________________________________________________
Note: After TC and SUT installations are complete, ensure that the time is the same on both systems. If the
times are not synchronized then see “Time Synchronization” in Troubleshooting section of the Appendix.
_______________________________________________________________________________________
20 After installing the Test Kit on TC then go to Section 2.2.3, “Setting up the DHCP/PXE server on TC”.
2.2.3 Setting Up the DHCP/PXE Server on TC
In System Test Kit 7, the Test Console (TC) system can function as a DHCP and PXE install server. The basic DHCP
and PXE functionality is enabled during the TC system Test Kit installation. We recommend that TC be used as a
PXE installation server, but this is optional. The steps below configure the TC as a PXE server. The next step is to
add SLES operating system iso images to the PXE install menu on TC. The SLES iso images are available from
https://download.suse.com/index.jsp. Adding the iso images to the TC can be done by two different methods. Please
choose method 1 or method 2 below. If a portable USB storage device is used to transfer the ISO files from a
windows system to a SLES system then the USB storage device will need to be formatted as a FAT file system. The
FAT file system can be read by both windows and by SLES, many other files systems cannot be read by both
operating systems.
Method 1:
The easiest process is to download the iso image then copy it onto media then copy the iso from the media onto
the TC. The directory which the ISO files are copied into must not contain a space in the directory name. A
flashdrive or a USB hard drive may be used to move the OS ISO image to the TC. We suggest placing them all in the
same directory.
25 Linux Test Suite

Method 2:
The ISO images can be generated from an OS installation DVD. The instructions below will create an ISO image
on the TC from a normal OS installation DVD. This process only works for a single OS DVD.
1 Obtain an installation DVD of the desired SLE version.

2 Place the installation DVD in the TC system DVD drive.
3 On the TC open a terminal, then type:
dd if= <DVD drive device entry> of=<desired name of iso image> bs=4k” <Enter>.
Example: dd if=/dev/sr0 of=./SLES-11-SP4-i586.iso bs=4k <Enter>.
The dd command will copy all data from the DVD media into the current directory. This will take time to
complete.
4 After copying the ISO images in to the TC then continue to Section 2.2.4, “Adding ISO images to the PXE menu
on TC”.
2.2.4 Adding ISO Images to the PXE Menu on TC

1 On the TC open a terminal, then type: configinstserver.sh <Enter>. The script can be found at:
/opt/suse/testKits/system/bin/configinstserver.sh
2 Type Y <Enter>.
3 Type “A” to add an image. The configinstserver.sh script will search for and display all iso images on the system.
________________________________________________________________________________________
Note: This PXE server configuration is set up for SLE products only. Do not add ISO images for operating
systems other than SLE products, even though the search will find other ISO's.
________________________________________________________________________________________
4 Enter the number of the iso image to be added.
5 If prompted to add a custom autoyast file answer N, unless you have a custom autoyast file to add.
6 Repeat steps 3 & 4 for each additional ISO image to be added. Up to 8 ISO images can be added.
7 Enter “Q” to exit the configinstserver.sh program.
8 Continue to Section 2.2.5, “Configuring the SUT for and using the PXE boot”.
2.2.5 Configuring the SUT For and Using the PXE Boot
We recommend UEFI OS boot be enabled on the SUT, if the SUT supports UEFI OS boot. This will permit UEFI to
be listed in the BIOS/UEFI field, otherwise BIOS must be listed. The PXE boot install is supported with a UEFI
enabled SUT for 64-bit SLES. For SLES installation on a secure boot enabled system please see section 6 entitled
“Manually installing SLES 12 or SLES 11” in this document. For 32 Bit SLES 11 (latest support pack) installations
the BIOS must be in legacy mode or the SLES OS must be installed manually with DVD (see section 6 entitled
“Manually installing SLES 12 or SLES 11”).
1 Attach all SUT network ports to TC through a hub or switch. Up to 16 NIC ports on a SLES SUT can be tested.
Ensure that SUT has no more than 16 NIC ports. Up to 8 NIC ports can be tested on a SLED SUT. The number of
26 Linux Test Suite

hubs or switches depends upon the number of NIC ports in SUT. If SUT has 1 NIC port then use 1 switch to connect
to TC. If the SUT has 2 NIC ports then use 2 switches. If the SUT has 3 NIC ports then use 3 switches. Otherwise
use 4 switches between TC and SUT. See figures 2-1 and 2-2 for servers or figure 2-3 for workstations and laptops.
2 Remove all external devices (USB, eSATA, Firewire, etc.) from the SUT.
3 Boot the SUT and enter the BIOS/UEFI configuration.
4 Ensure that network boot (PXE) is enabled in the BIOS/UEFI. If needed , press the appropriate key to enter the
BIOS/UEFI and select the PXE boot during post.
5 PXE boot the SUT.

6 The SUT will display a PXE menu which includes the option "SUSE SCK Menu". If the SUT does not display any
menu, or if the SUT displays a PXE menu which does not include the “SUSE SCK Menu” option, then the SUT is
not connected to the TC system or the SUT may not support PXE boot. Check the LAN cables for correct wiring to
the secluded/isolated network. Repeat the steps 1 through 4 to address this problem.
7 If displayed, select the "SUSE SCK Menu" option and press <Enter>.
8 The SUSE SCK Menu will display the different operating systems that the user may choose to install. If the SUSE
SCK Menu does not display the desired operating system, repeat the steps in Section 2.2.3, “Setting up the
DHCP/PXE server on TC” then Section 2.2.4, “Adding ISO images to the PXE menu on TC” above. Each
operating system will have multiple install options displayed in the SCK Menu. For example:
SLES11_SP4 x86_64 single disk automated install

SLES11_SP4 x86_64 multiple disks automated install
SLES11_SP4 x86_64 manual install
Each option is briefly explained below.

a) single (hard) disk automated install – This option is appropriate for most servers and workstations which
have a single hard disk drive or a RAID configuration which appears as a single hard drive. All OS
installation settings are completed for the user.
b) multiple (hard) disk automated install – This is the same as single-disk install except the user will be
provided with the ability to configure disk partitions and specify OS installation location.
c) manual install (Recommended for SLE 12 SP3) – The manual OS installation is like a DVD install. The
user inputs all settings for each configuration screen during the install. We recommend this installation
method for SLE 12 SP3 installations to ensure that the kdump values are set.
d) laptop automated install (not displayed in the example above) - This option is appropriate for most
notebooks/laptops. This choice is similar to the single hard drive.
9 Proceed to section Section 2.3, “Setting up the SUT”
27 Linux Test Suite

2.3 Setting Up SUT
The following instructions are for installing SLES on the SUT.
2.3.1 Installing SLE on SUT Through PXE

1 With the SUSE SCK Menu displayed on SUT use the arrow keys (or the tab keys on some systems) to select the OS
to install, then press <Enter>. There is a short delay after pressing enter then SUT will display the SLE GUI
Installation screen then begin the OS installation automatically.
____________________________________________________________________________________________
Note: The second Xen Guest installation must be a fully virtualized (FV) SLES guest and must be installed via
DVD media. This is necessary so that the optical test will be set up correctly.
____________________________________________________________________________________________
2 If single (hard) disk automated install was selected then proceed to Section 2.4, “Installing the Test Kit on
the SUT”.
3 If manual installation was selected then proceed to the documentation section which matches your choice. The
sections are as follows:
Section 3, “Manually Installing SLED 12 SP3”

Section 6, “Manually Installing SLES 12 or SLES 11”
4 If multiple (hard) disk automated install was selected then follow the steps below:
For SLE 11 do the following:
4a The SUT installation will stop at the "Installation Settings" screen. Do NOT modify the "Software" or
"Language" settings. The automated installation includes the correct settings.
4b Select Installation Settings > Partitioning.

__________________________________________________________________________________________
Note: For each partition, make sure to use the default file system/format type. The system Test Kit is designed
to function with the default file system types.
__________________________________________________________________________________________
4c Select Hard Disks or RAID in the System View window and select the disk you want to partition.
4d Click the Add... button at the bottom of the Hard Disk: window.
4e Click the Primary partition radio button.
4f Click Next to accept the primary partition.
4g Click Next to accept the Maximum Size as the new partition size.
4h Assign a mount point to the hard drive or RAID device. The following suggestions may be used for the
mount points:
For a hard drive, change the mount point to /media/sut/hdx where x= the number of the hard disk (e.g. Hd2, hd3,
hd4, ..., hd16) TestConsole uses HD1 for the first hard disk. For a RAID, change the mount point to
/media/sut/raidx where x= the number of the RAID array (e.g. Raid2, raid3, ..., raid16) TestConsole uses RAID1
for the first hard disk.
28 Linux Test Suite

4i Click Finish to create the primary partition formatted with ext3 for the entire disk space.
4j If prompted select OK to the “changes in disk partition...” question.
4k Repeat these steps (4c-4i) for each device that hasn't been partitioned.
4l Click Accept to return to the Installation Settings screen.
4m Click install, then click accept, the install.
4n The SUT automated installation will continue.
5 The SUT will reboot during the install. After the install has completed, the GUI login screen will be displayed.
Proceed to section Section 2.4, “Installing the Test Kit on the SUT”.
en) 6 April 2007
2.4 Installing the Test Kit on the SUT

The following steps are to be used to install the Test Kit on SUT.
______________________________________________________________________________________________
Note: If installing the Test Kit onto a XEN/KVM VM where PCI-Pass-Through or SR-IOV is going to be configured,
please manually set a static IP address on the 10.1.2.x network before installing the Test Kit. The Test Kit will then be
able to create all necessary configuration files on the correct network without issues.
______________________________________________________________________________________________
1 On SUT log in as root, the password is suse.

2 A terminal window will display the System Test Kit install prompt.
3 Choose the appropriate Test Kit installation. Choose 1 for “SUT System” install for SLED, or SLES, or a KVM
Host, or a KVM Guest or a Xen Host by pressing 1 <Enter>.
Or
Choose 2 for “Xen Guest” install for a Xen guest by pressing 2 <Enter>.
4 If prompted, enter the IP address of TestConsole (default = 10.1.1.2) then press <Enter>.
5 When prompted, enter the password of TestConsole (i.e. suse) then press <Enter>.
6 The NIC Configuration Menu will appear. The proposed SUT IP address numbers will be listed. Follow the
onscreen instructions. The purpose of this menu is to confirm or change the assigned IP address information. Also to
ensure that an existing NIC management only port is not assigned an IP address for NIC testing. Remove any IP
address assigned to the NIC management only ports by typing/assigning do_not_test. Change the IP address
information as needed by typing the NIC number (example: 1) then press <Enter> then enter the IP address. Press C
<Enter> if the displayed information is correct and all changes have been made. For a Xen VM Guest or KVM
Guest, the default IP addresses are as follows:
______________________________________________________________________________________
Guest (virtual machine) System IP Address
__________________________________________________________________________________________
VM Guest 1 10.1.1.11
VM Guest 2 10.1.2.12 (If supported by the NIC, this VM is used for PCI
Pass-through /SRIOV)
VM Guest 3 10.1.1.13
29 Linux Test Suite

VM Guest 4 10.1.1.14
Windows VM Guest 5 10.1.1.15
__________________________________________________________________________________________
_______________________________________________________________________________________
Note: You should verify that nmap detected each of the IP addresses expected. A warning will be reported if
no additional IP addresses are found on the network segment.
_______________________________________________________________________________________
7 When prompted, enter the password for SUT (i.e. suse) then press <Enter>.
8 Once the Test Kit installation has completed, press <Enter> when prompted.
9 On SLES 11(latest SP), if needed configure the display resolution using the steps below:
9a Open a terminal window.
9b Type sax2 -r<Enter>.
9c Set or accept the monitor resolution.
9d Click OK.
9e Test the configuration if desired, then save.
9f Click Yes to exit sax2.
9g Restart the server to load the new display settings.
9h Log in as root, the password will be suse.
10 If the SUT is SLES 11 (latest support pack) follow the steps below to set the time display.
10a For SLES 11 Right-click on the time display in the Display panel.
10b Click Preferences.
10c Select 12 hour in the box next to Clock Format on SLES 11.
10d Select Show Seconds.
10e Click Close.
11 If the SUT is SLES 12 (latest support pack) follow the steps below to set the time display.
11a Right-click on the speaker in the bottom right of the Display panel.
11b Click on the round button which has the screw driver and the wrench inside.
11c Click Date and Time.
11d Select AM/PM in the drop down box next to Time Format.
11e Click on the x in the upper right corner to Close the window.
____________________________________________________________________________________________
Note: Time synchronization may take up to 2 hours. After SUT, and TC installations are complete, ensure that the
time is the same on both systems. If the times not are synchronized then see “Time Synchronization” in the
Troubleshooting section of the Appendix.
____________________________________________________________________________________________
12 If this installation was a SLES Xen Host (host server) then the Virtual Machine documentation URL's are
referenced below. The Xen documentation for SLES 11 is called the “Virtualization Guide” and is available at:
30 Linux Test Suite

https://www.suse.com/documentation/sles11/book_xen/?page=/documentation/sles11/book_xen/data/book_xen.html
For the Xen Host install, which should now be completed, go to Section 2.5, “Updating the Products.txt file” to
begin the base non-xen certification testing. Once the base certification testing is complete, then goto to Chapter 4,
“Xen Virtual Machine Tests” to set up the Xen virtual machines.
13 If this installation was for a SLES 11 SUT or a SLES 12 SUT or a SLED 12 SUT, and TC is configured, then go to
Section 2.5, “Updating the Products.txt file”.
14 If this installation was for a SLES 11 or 12 Xen guest then to install additional Xen guests repeat section Section
4.1, “Installing a Virtual Machine”. If all 3 Xen guests have been installed continue to “Section 4.2, “Using SLES
Virtual Machines”.
15 If this installation was for a SLES 11 or 12 KVM Host and TC is configured, then go to Section 2.5, “Updating the
Products.txt file” to begin the base non-KVM certification testing.
16 If this installation was for a SLES KVM Guest and the Network PCI pass-through has not been configured then
goto Section 5.5, “Configuring KVM for Network PCI Pass-Through”. Otherwise if an additional KVM Guest is
needed to be installed then repeat Section 5.2, “installing the Kernel based machine”. If all KVM Guest's have
been installed then continue to Section 2.5, “Updating the Products.txt file” .
31 Linux Test Suite

2.5 Updating the Products.txt File
The products.txt file is used by TC to make the latest hardware in the SBS database (example: CPU, video adapter,
HBA, storage device and NIC) available for selection when entering the SUT system information. The products.txt
file can be updated via the Internet or other removable storage (example: flash drive).
__________________________________________________________________________________________
Note: In order to display the new hardware selections TestConsole must be closed then re-opened after the
products.txt is updated.
__________________________________________________________________________________________
2.5.1 Updating by Internet

If the TC system has Internet access, do the following:
1 Double-click the TestConsole icon on the TC desktop.
2 Click Console > Update Products.txt from the main menu. If the Help window appears, click Ok.
3 Verify that the products.txt was updated.
3a Click Help > About TestConsole from the main menu.
3b Verify that the date displayed at the bottom of the window is within a 2 days of the current date.
3c Click OK.
4 Close TestConsole. Open TestConsole. The product.txt update is now complete.
2.5.2 Updating with Other Media

If the TC system does not have Internet access, do the following to update the products.txt:
1 Download the latest products.zip file.
1a Using a system with Internet access, download the latest products.zip from the YES System Test Tools for
SUSE Linux webpage (https://www.suse.com/partners/ihv/yes/system-test-tools-for-suse-linux.html) .
1b Copy the products.zip file to a removable storage device.

2 Insert the removable storage device containing the products.zip file into the TC system.
3 Double-click the TestConsole icon on the TC desktop.
4 If the Products.txt Update Help window is not displayed, click Console > Update Products.txt from the menu bar.
5 In the Select Products.zip window click the down arrow (↓) next to Look in:.
6 Select the / character.
7 Double-click on Media.
8 Double-click on the removable storage device containing the products.zip file.
9 Click on the Products.zip file.
10 Click Save. The products.zip file should now be updated.
11 Click OK at the Products.txt Update Help window.
12 Unmount and remove the removable storage device.
32 Linux Test Suite

13 Close TestConsole by clicking on the x in the upper right corner. Click on Yes to really quit.
14 Open TestConsole by clicking the TestConsole icon located on the TC desktop. The product.txt update is now
complete. Ensure that the TestConsole screen is in full screen mode so that the date and time information for the
products.txt file will be displayed in the bottom of the TestConsole window.
15 Continue to the next section.
33 Linux Test Suite

2.6 Creating a New Test Project
1 Ensure you have updated the products.txt file (see Section 2.5, “Updating the Products.txt File”).
________________________________________________________________________________________
Note: Direct Access to the TC, and SUT systems are required (do not use remote access, do not use SSH).
________________________________________________________________________________________
2 Click the New button on the menu bar.

3 Click on the appropriate project then click Select
• SLED 12 Workstation - Full
• SLED 12 Laptop – Full
• SLED 12 Workstation - Reduced (See the Reduced Testing Policies located at
https://www.suse.com/partners/ihv/pdf/System_Certification_Policies.pdf Website to determine eligibility to
use this test project).
• SLES 11/12 Server - Full

• SLES 11/12 Server - Reduced (See the Reduced Testing Policies located at
use this test project.)
• Virtualization-Full – For testing XEN, KVM and Third party Hypervisor with SLES 11 & 12 (Prerequisite:
Requires a complete SLES only system certification prior to XEN and KVM testing). After the project has
been created choose to Test SLES 11, or Test SLES 12 SP1, or Test SLES 12 SP3 or Test Third-Party
Hypervisor.
• Virtualization-Reduced – For testing XEN, KVM and Third party Hypervisor with SLES 11 & 12
(Prerequisite: Requires a complete SLES only system certification prior to Xen testing and see the Reduced
Testing Policies located at
use this test project). After the project has been created choose to Test SLES 11, or Test SLES 12 SP1, or Test
SLES 12 SP3 or Test Third-Party Hypervisor.
4 A default unique project file-name will be generated. The unique project file-name contains a date-stamp and time-
stamp. You may choose a different unique project file-name by typing a file-name into the project file name field.
Click on Save to save the project. Please use a unique project file-name which has not been used previously.
_________________________________________________________
Note: Do not put spaces or html control characters or periods in the file-name.
_________________________________________________________
5 Follow any onscreen prompts.

6 For Virtualization-Full or Virtualization-Reduced double click the box for the type of testing being performed. The
choices will be: Test SLES 11 XEN or KVM Host, Test SLES 12 SP1 XEN or KVM Host, Test SLES 12 SP3 XEN
or KVM Host, or Test 3rd Party Hypervisor.
7 Continue to the IP address Information section.
34 Linux Test Suite

(en) 6 April 2007
2.7 IP Address Information
1 Review the IP addresses listed in the Project Contents window for SUT, and TC.
2 If the IP address for SUT is incorrect, do the following:
2a Double-click the SUT IP address.
2b Enter the correct IP address in the Selection field.
2c Click OK.
3 If the IP address for TC is incorrect, do the following:
3a Double-click the TC IP address to be changed.
3c Click OK.
3d Repeat steps 3a, 3b, and 3c, for each TC IP address which needs to be changed.
4 The test projects for SLES start with 2 NIC tests enabled on SUT and on TC. Only the first NIC is ever displayed in
the test project for SUT. Up to 16 NIC tests can be enabled in the SLES projects. The 16 NICs will be displayed
for the TC IP addresses. The TC will find the NIC ports on SUT as long as the IP addresses have been defined on
SUT as instructed in the SUT installation section. All NIC ports in the SUT are expected to be assigned an IP
address and to be tested. To enable additional NIC tests on TC beyond the first 2 NIC ports, repeat the following for
each additional NIC:
4a Double-click Enable NIC x Test (where x is the number of the NIC).
4b If the IP address for NIC x (where x is the number of the NIC) is incorrect then double click on it to edit the
IP address.
__________________________________________________
Note: The NIC tests will be run together during the stress test.
__________________________________________________
4c To disable a NIC which may have been accidentally enabled, click on disable NIC x (where x is the number of
the NIC) test.
5 For SLED workstations containing only wired NICs: the test project for SLED will start with 1 NIC test enabled.
Up to 8 NIC tests can be enabled for the SLED projects. SLED will typically allow only 1 NIC to be enabled at a
time. To enable additional NIC tests beyond the first NIC, repeat the following for each NIC:
5a Double-click Enable NIC x Test (where x is the number of the NIC).
IP address.
________________________________________________________________________________________
Note: The NIC tests will be run together during the stress test. The SLED OS may limit the number of NICs
to be enabled.
________________________________________________________________________________________
6 For SLED testing which includes wireless NIC testing: the test project for the SLED Workstation and SLED Laptop
start with 1 NIC test enabled for the wired NIC test. SLED will typically allow only 1 NIC to be enabled at
a time. If a wireless adapter exists then the tester should run through the testing for the wired NIC test (2 hours)
35 Linux Test Suite

before switching to the wireless NIC on the SUT. The wireless NIC test is part of the stress test. After the wired
NIC tests are completed the tester must disable the wired NICs, then enable the wireless NIC. The wired NICs can
be disabled by unplugging the Ethernet cable. A total of 2 wired NICs and 1 Wireless NIC can be enabled in the
SLED workstation project and the SLED laptop project for testing. To enable the additional NIC tests, do the
following:
6a Double-click Enable NIC 2 Reduced Test and/or Enable Wireless NIC Test.
IP address.
_______________________________________________________________________________________
Note: The Wireless NIC Test is required on all systems which have a built-in or ship with a wireless NIC.
_______________________________________________________________________________________
36 Linux Test Suite

2.8 Xen Virtual Machine Tests Setup
These steps are only for testing a Xen virtual machine. The xen guests should be installed before testing the Xen
virtual machine (See section 4 for instructions to set up a xen virtual machine). Only the “SLES - Xen Server – Full”
and the “SLES - Xen Server – Reduced” projects will contain the Xen VM listings.
If you have chosen a different project, skip this section.
Figure 2-8 Xen Project Information
37 Linux Test Suite

The steps below apply to XEN and KVM configurations.
1 The test tools automatically enable the 3 VM Guest IP addresses. Review the IP addresses listed in the Project
Contents window for VM 1, VM 2, and VM 3.
2 If the IP address for Guest VM 1 is incorrect, do the following:

2a Double-click the Guest VM 1 IP address.
2c Click OK.
3 If the IP address for Guest VM 2 is incorrect, do the following:
3c Click OK.
4 If the IP address for Guest VM 3 is incorrect.
4c Click OK.
5 Up to 4 SLES VM's can be enabled for testing plus 1 Windows VM.
2.9 Validate Install Test

Test Objective: Verify that SLES or SLED with the latest service pack will install on the SUT. All subsequent tests
will be available once the validate install test and component check test are completed. Please note that the Validate
Install test may take up to 35 minutes. If you are testing Xen guests (Xen Virtual Machines), then repeat this test for
each of the Xen Virtual Machines. If you are testing Kernel Virtual Machines (KVM's), then repeat this test for each
of the Kernel Virtual Machines (KVM's).
x (en) 6 April 2007
When testing SLED (latest service pack) on a SUT that includes a wired and wireless adapter, the WIRED adapter
should be configured as the active adapter during the following tests:
• Validate Install test

• Component Check
• Laptop Tests
• Power Management Tests
• Verify NIC 1
• NIC 1 Reduced Test
• Verify Time Sync Setup
1 Double-click Validate Install Test under the TestConsole project for the SUT.
2 If prompted, answer the IP address questions.
3 If prompted, answer Yes to the “Install the Kit?” question.
38 Linux Test Suite

2.10 Component Check Test
This test will gather system information about the SUT. Ensure that all devices (e.g. wireless LAN adapter) are
enabled before starting the Component Check Test. Any changes made to SUT (hardware, drivers, BIOS/firmware
updates) after this test is run will not be detected in the system information screens. It is important that all hardware,
drivers, BIOS/firmware updates which will be used during testing are installed on the SUT before starting the
Component Check Test. All subsequent tests will be available once the validate install test and component check test
are completed. If a detected component is deleted from the detected devices it can be listed again by starting the
component check test again. Direct access to the TC, and SUT systems are required (do not access remotely, do not
use SSH).
1 Double-click Component Check in the Project Contents pane.

2 Follow any on-screen prompts on TC.
3 Click Yes on the Open Edit Product/Report pop-up window.
2.11 Product and Report Information Entry

The Product and Report Information screen is the product information input tool for your Yes Certification Bulletin.
The hardware information entered on the following screens will be the same information which appears on your Yes
Certification bulletin. Please be accurate with all inputted information.
_______________________________________________________________________________________
Note: Direct access to the TC, and SUT systems are required (do not access remotely, do not use SSH).
_______________________________________________________________________________________
1 Click the Edit Product/Report button to open the Product & Report Information window.
2 Proceed to section 2.11.1 System Information.
39 Linux Test Suite

2.11.1 System Information Entry
The system information consists of all fields under the System tab. Much of the OS detected information will be
filled in automatically. The fields are editable and can be corrected as needed. This is the information which will
appear on the Yes Certification Bulletin. It is important to complete all information entry in section 2.11 accurately
before testing the SUT.
Figure 2-3 System Tab
______________________________________________________________________________________________
WARNING: Ensure that all fields are filled out in the System tab before starting tests. Test Results will be cleared if
these fields are changed (with the exception of the Product Description field and Configuration Note field). The
system information fields are required to be completed for the test results submission file to successfully read into the
SUSE Bulletin System (SBS).
______________________________________________________________________________________________
40 Linux Test Suite

1 Enter the System Information. The detectable information will be filled in automatically.
1a If missing or incorrect, enter the System Name and Model.
1b If missing or incorrect, choose the Computer Type from the drop down list.
1c If missing or incorrect, enter the Mother Board Revision.
1d If missing or incorrect, enter the system BIOS/UEFI version information. There are three possible options to be
reported in the BIOS / UEFI field: UEFI, BIOS or UEFI-Legacy.
Examples: UEFI: AJ152 (12/24/2013)
BIOS: AJ152 (12/24/2013)
UEFI-Legacy: AJ152 (12/24/2013)
Edit this field to be the correct information. The line must display one of the following:
A UEFI: <version> <date> - This means that the firmware on the hardware platform is UEFI and the system
was booted in its UEFI enabled configuration. It also means that the SLES OS on the SUT was installed
and booted using the UEFI boot loader (ELILO).
or
B BIOS: <version> <date> - This means that the firmware on the hardware platform is a traditional BIOS
and the system was booted through the BIOS. It also means that the SLES OS on the SUT was installed
and booted using the traditional or legacy boot loader (GRUB).
or
C UEFI-Legacy: <version> <date> - This means that the firmware on the hardware platform is UEFI and
was booted UEFI. It also means that the SLES OS on the SUT was installed and booted using the
traditional or legacy boot loader (GRUB).
1e If missing or incorrect, enter the system Memory (RAM) then choose from the drop-down the units of measure
(e.g., Megabytes, Gigabytes, etc.). If the testing is for XEN, KVM or Third party Hyperviser then the RAM
needs to list the RAM assigned to the host platform, the RAM assigned to the VM Guests, and the RAM
assigned to the Single Max VM Guest. An example is below:
Host Platform: 2048 GB, 64-bit VM Guests: 678 GB, Single Max VM 64-bit Guest Tested Memory: 2034 GB
41 Linux Test Suite

2 Select the CPU in the SUT.
Figure 2-4 CPU Selection Window
2a Click the ‘+' button next to the CPU’s field.

2b Select the appropriate CPU from the filter list. The short list of the closest detectable matching CPU/s will be
listed on the screen. If this is the correct CPU and the quantity which is in your SUT then click on the CPU to
select it. Then click OK.
2c If needed use a search filter to find the CPU in the SUT. If the correct CPU was not detected, there are 3
additional filter methods to use when searching for the CPU. The CPU should be selected from the results
when using any of these filters. The filter types are: previously selected, short list, long list, and search all
CPU's. These can be selected by clicking on the associated radio button on the screen. Below is an explanation
of each filter.
42 Linux Test Suite

Previously Selected - This filter will display all CPU's previously used.
Short List - This is the default filter when the screen is opened. The CPU/s containing all of the auto detected
criteria will be displayed.
Long List - The CPU/s containing any part of the auto detected criteria will be displayed.
Search all CPU's - This is an editable interactive search filter. The editable search field will appear. Enter any
information to search on. If no search criteria is entered, then all CPU's will be listed.
If the correct CPU still does not appear in the filter list after using each of the search filters, then choose a
substitute CPU for testing. Propose the new unlisted CPU in SBS. See the SBS users guide in the Appendix of
this document for more information.
2d The CPU quantity will also be automatically filled in. If CPU quantity is missing or incorrect, then enter the
correct quantity.
2e To remove a CPU, select a different CPU.
2f Click OK.
3 Enter the Product Description

The product description field on a YES CERTIFIED bulletin is a way to include additional information about your
product that is important, but that is not listed elsewhere on the bulletin.
Requirements for the Product Description:

• Product description must be in English and may not exceed 1,000 characters.
• Do not use carrots < > in the product description.
• Do not use special characters such as trademarks or copyrights in the product description.
• Do not make claims that are difficult or impossible to substantiate, especially over time.
Some examples include the following:

• Do not use phrases like “this is the best...”, “fastest...”, etc.)
• Do not make statements about product lines or product series. It must be specific to the product tested and the
configuration listed in the specific bulletin.
• Do not compare your product to a competitor’s product or with other products on the market.
• If a component category is not listed on the bulletin in the tested configuration area, but was part of the tested
configuration, it may be included in the product description.
• Do not indicate optional adapter/driver configurations. A separate bulletin is required for the adapter / driver
pair.
• Do not list alternate processor family, unless test results are submitted for these alternate processors.
• If alternate configurations of components are available and desired on a bulletin (video, hard drives,
keyboards, etc.), then a separate bulletin must be created. If it is desired to list a “variety of options” (hard
drives, optical drives, etc. are available), then each must have a separate bulletin.
_________________________________________________________________________________
43 Linux Test Suite

Note: SUSE reserves the right to remove any information from the bulletin submission that is
deemed questionable with regards to this process at its own discretion.
_________________________________________________________________________________
• Any required installation or configuration instructions should not be in the product description, but should
instead be included in the configuration notes section of the bulletin.
To provide additional marketing information about your product, the following options are provided:
• A URL where additional product information can be obtained can be included in the product description.
Note that the bulletin becomes a static document, so use a link that is not likely to change (you may want to
use your company Web site).
4 Enter configuration notes into the Configuration Note field. Configuration Notes may also be added to the Yes
Certification Bulletin after the bulletin submission is read into the SBS database.
• If any boot parameters were used for the OS Installation on the SUT, please enter this information into the
Configuration Note field.
• If the certification testing is for Xen, then please provide the Base SLES bulletin number in the configuration
note or enter the information into the communications section of the bulletin submission in SBS.
• Add any configuration information that an end-user would need to know when using the system.
2.11.2 Company Information

The company information consists of all fields under the Company tab.
1 Select the Company tab.

2 Enter the system manufacturer company name.
2a Click the ‘+' next to the Company field.
2b Select the company name by clicking on it. The first time that a company name is selected it will automatically
be entered into the testing company name field.
_______________________________________________________________________________________
Note: If your company name is not listed in the company drop down selection list then choose
“No Company Selected” from the list. Your company will be automatically added to the products.txt once
your company has a bulletin submission in SBS with your company name listed. See the SBS users guide
located in this document for more about adding a company to SBS.
_______________________________________________________________________________________
2c Click Select.
3 Change the Testing Company name if it is different from the system manufacturer company name.
3a Click the ‘+' next to the Testing Company field.
3b Select the testing company name by clicking on it.
3c Click Select.
4 Type in the Company URL (optional).
44 Linux Test Suite

2.11.3 Ports and Bus Information
1 Click the Port/Bus tab.
2 The ports and bus types will be auto populated by the detected system information. If the auto populated
information is not accurate, the list can be changed.
To add ports or bus types and edit the quantity of ports or bus types:
2a Click Add.
2b Click on the SUT's bus type or serial port, or USB port, or firewire port, etc. to be added.
2c Enter the quantity of ports or slots on the SUT.
2d Click OK.
To remove ports or bus types:

2e Click on the bus or port to remove.
2f Click Remove.
2g Follow the on screen prompt.
To edit ports or bus types and the quantity:

2h Click on the bus or port to edit.
2i Click edit.
2j Enter the quantity of ports or slots on the SUT.
2k Click OK.
45 Linux Test Suite

3 Repeat the steps above for each BUS or serial port, or USB port, or firewire port, in the SUT.
Figure 2-5-1 Port and Bus Tab
46 Linux Test Suite

Figure 2-5-2 Port and Bus Selection Window
47 Linux Test Suite

2.11.4 Video, LAN, HBA and Storage Device Information
1 Select the Video Adapter used in the SUT.
1a Click the Video tab.
1b Click on the first video adapter listed.
1c Click edit in the Video Tab window.
1d Select the appropriate video adapter from the filter list. Any previously selected video adapter will be listed on
the screen. If this is the correct video adapter and quantity which is in your SUT then click on the displayed
video adapter to select it, then click OK. Repeat the steps in 1 for each video adapter. If the video adapter
which is in the SUT is not being listed then go to step 1e.
1e Use a search filter to list the video adapters to choose from. If the correct video adapter was not detected,
there are additional search filters to use when searching for the correct video adapter. The video adapter should
be selected from the results when using any of these filters. The filter types are: previously selected, short list,
long list, and search all devices. These can be selected by clicking on the associated radio button on the screen.
Below is an explanation of each filter.
Previously Selected - This is the default filter when the screen is opened. This filter will display all video
adapter 's previously selected.
Short List - The video adapter containing all of the auto detected criteria will be displayed.
Long List - The video adapter/s containing any part of the auto detected criteria will be displayed.
Search all Devices - This is a editable interactive search filter. The editable search field will appear. Enter any
information to search on. If no search criteria is entered, then all video adapter's will be listed. You may want
to search for part or all of the device or name. For example to search for an NE 2000, search for NE or 2000.
Or search for the Company or ID number.
Propose New Device (not found in database) - This is the method used to propose new video adapters. If the
video adapter cannot be found, then it must be proposed as new adapter.
1f If the video adapter cannot be found with the filters, then it must be proposed as a new adapter which is not
already contained in the SBS database.
1f1 Click on the Propose new device radio button.
1f2 Enter the video adapter product name.
1f3 If the device type listed is not correct then select the correct device type from the drop down choices.
1f4 Click on the Manufacturer drop down to select the video adapter manufacturer.
1f5 Click OK.
1f6 After the bulletin submission file is read into SBS, a manufacturer URL will need to be added for the
proposed device. See the SBS Users Guide in the Appendix of this document for more information about
adding a URL.
1g The video adapter quantity will also be automatically filled in. If video adapter quantity is missing or incorrect,
then enter the correct quantity.
1h Click OK. Repeat the video selecting steps until all video devices in the SUT are selected.
1i To remove a video adapter, click the Edit Product/Report button. Click on the video tab. Click on the video
adapter to remove, then click remove. Follow the onscreen prompts.
48 Linux Test Suite

1j To restore a deleted video adapter, close the Product & Report Information screen by clicking on the OK button
at the top right. Double-click Component Check in the Project Contents pane. Click on the Edit Product/Report
button. Click on the video tab. The removed video driver will be listed. Repeat the video selecting steps until
all video's are selected.
Figure 2-6-1 Video Tab
49 Linux Test Suite

Figure 2-6-2 Video Edit/Selection Window
2 Select the LAN Adapter/s used in the SUT.

2a Click the LAN tab.
2b Click on the first LAN adapter listed.
2c Click edit in the LAN Tab window.
2d Select the appropriate LAN adapter from the filter list. Any previously selected LAN adapter will be listed on
the screen. If this is the correct LAN adapter and quantity which is in your SUT then click on the displayed LAN
adapter to select it, then click OK. Repeat the steps in 2 for each LAN adapter in the SUT. If the LAN adapter
which is in the SUT is not being listed then go to step 2e.
2e Use a search filter to list the LAN adapters to choose from. If the correct LAN adapter was not detected,
50 Linux Test Suite

there are additional search filters to use when searching for the correct LAN adapter. The LAN adapter should be
selected from the results when using any of these filters. The filter types are: previously selected, short list, long
list, and search all devices. These can be selected by clicking on the associated radio button on the screen.
Below is an explanation of each filter.
Previously Selected - This is the default filter when the screen is opened. This filter will display all LAN
adapter's previously selected.
Short List - The LAN adapter containing all of the auto detected criteria will be displayed.
Long List - The LAN adapter/s containing any part of the auto detected criteria will be displayed.
Search all Devices - This is a editable interactive search filter. The editable search field will appear. Enter any
information to search on. If no search criteria is entered, then all LAN adapter's will be listed. You may want
to search for part or all of the device or name. For example to search for an NE 2000, search for NE or 2000. Or
search for the Company or ID number.
Propose New Device (not found in database) - This is the method used to propose new LAN adapters. If the
LAN adapter cannot be found, then it must be proposed as a new adapter.
2f If the LAN adapter cannot be found with the filters, then it must be proposed as a new adapter which is not
already contained in the SBS database.
2f2 Enter the LAN adapter product name.
2f4 Click on the Manufacturer drop down to select the LAN adapter manufacturer.
2f5 Click OK.
adding a URL.
2g The LAN adapter quantity will also be automatically filled in. If LAN adapter quantity is missing or incorrect,
then enter the correct quantity.
2h Click OK. Repeat the LAN selecting steps until all LAN's in the SUT are selected.
2i To remove a LAN driver or LAN adapter, click the Edit Product/Report button. Click on the LAN tab. Click on
the LAN driver or LAN adapter to remove, then click remove. Follow the onscreen prompts.
2j To restore a deleted LAN driver, close the Product & Report Information screen by clicking on the OK button
at the top right. Double-click Component Check in the Project Contents pane. Click on the Edit Product/Report
button. Click on the LAN tab. The removed LAN Driver will be listed. Repeat the LAN selecting steps until all
LAN's in the SUT are listed.
51 Linux Test Suite

Figure 2-7-1 LAN Tab
52 Linux Test Suite

Figure 2-7-2 LAN Edit Window
3 Select the HBA used in the SUT.

3a Click the HBA tab.
3b Click on the first HBA listed.
3c Click edit in the HBA Tab window.
3d Select the appropriate HBA from the filter list. Any previously selected HBA will be listed on the screen. If this
is the correct HBA adapter and quantity which is in your SUT then click on the displayed HBA to select it, then
click OK. Repeat the steps in 3 for each HBA. If the HBA which is in the SUT is not being listed then go to step
3e.
53 Linux Test Suite

3e Use a search filter to list the HBA to choose from. If the correct HBA was not detected, there are
additional search filters to use when searching for the correct HBA. The HBA should be selected from the results
when using any of these filters. The filter types are: previously selected, short list, long list, and search all
devices. These can be selected by clicking on the associated radio button on the screen. Below is an explanation
of each filter.
Previously Selected - This is the default filter when the screen is opened. This filter will display all HBA's
previously selected.
Short List - The HBA containing all of the auto detected criteria will be displayed.
Long List - The HBA containing any part of the auto detected criteria will be displayed.
Search all devices - This is a editable interactive search filter. The editable search field will appear. Enter any
information to search on. If no search criteria is entered, then all HBA's will be listed. You may want to search
for part or all of the device or name. For example to search for an NE 2000, search for NE or 2000. Or search
for the Company or ID number.
Propose New Device (not found in database) - This is the method used to propose new HBA. If the HBA
cannot be found, then it must be proposed as a new adapter.
3f If the HBA cannot be found with the filters, then it must be proposed as a new adapter which is not already
contained in the SBS database.

3f2 Enter the HBA product name.
3f4 Click on the Manufacturer drop down to select the HBA manufacturer.
3f5 Click OK.
adding a URL.
3g The HBA quantity will also be automatically filled in. If HBA quantity is missing or incorrect, then enter the
correct quantity.
3h Click OK. Repeat the HBA selecting steps until all HBA's in the SUT are selected.
3i To remove an HBA, click the Edit Product/Report button. Click on the HBA tab. Click on the HBA driver or
HBA to remove, then click remove. Follow the onscreen prompts.
3j To restore a deleted HBA or HBA driver, close the Product & Report Information screen by clicking on the OK
button at the top right. Double-click Component Check in the Project Contents pane. Click on the Edit
Product/Report button. Click on the HBA tab. The removed HBA driver will be listed. Repeat the HBA
selecting steps until all HBA's in the SUT are selected.
54 Linux Test Suite

Figure 2-8-1 HBA Tab
55 Linux Test Suite

Figure 2-8-2 HBA Edit/Selection Window
4 Select the storage devices in the system (this includes hard disk drives, optical media drives, SAN's and backup
drives).
4a Click the Device tab.

4b Click on the first device listed.
4c Click edit or if the device is unlisted click add in the Device Tab window.
4d Select the appropriate device from the filter list. Any previously selected device will be listed on the screen. If
this is the correct device which is in your SUT then click on the displayed device to select it. If the device which
is in the SUT is not being listed then go to step 4e.
56 Linux Test Suite

4e Use a search filter to list a device to choose from. If the correct device was not detected, there are
additional search filters to use when searching for the correct device. The device should be selected from the
results when using any of these filters. The filter types are: previously selected, short list, long list, and search all
devices. These can be selected by clicking on the associated radio button on the screen. Below is an explanation
of each filter.
Previously Selected - This is the default filter when the screen is opened. This filter will display all device's
previously selected.
Short List - The device containing all of the auto detected criteria will be displayed.
Long List - The device/s containing any part of the auto detected criteria will be displayed.
Search all devices - This is a editable interactive search filter. The editable search field will appear. Enter any
information to search on. If no search criteria is entered, then all device's will be listed. You may want to search
for part or all of the device or name. For example to search for an NE 2000, search for NE or 2000. Or search for
the Company or ID number.
Propose New Device (not found in database) - This is the method used to propose new device. If the device
cannot be found, then it must be proposed as a new adapter.
4f If the device cannot be found with the filters, then it must be proposed as a new device which is not already
contained in the SBS database.
4f2 Enter the device product name.
4f4 Click on the Manufacturer drop down to select the device manufacturer.
4f5 Click OK.
adding a URL.
4g The device quantity will also be automatically filled in. If device quantity is missing or incorrect, then enter the
correct quantity.
4h Click OK. Repeat the device selecting steps until all device's in the SUT are selected.
4i To remove a device, click on the device, then click remove.
57 Linux Test Suite

Figure 2-9-1 Devices Tab
58 Linux Test Suite

Figure 2-9-2 Devices Edit/Selection Window
59 Linux Test Suite

Figure 2-9-3 Devices Add Window
60 Linux Test Suite

5 Check for hardware that has not been added to the SUT hardware information list.
5a Click Verify in the Product & Report Information window to review the Errors.
5b If there are any “ERROR … Missing...: “ messages do the following:
5b1 Write down the missing devices. Follow the instructions in section 2.11.1, 2.11.2, 2.11.3 and 2.11.4 to add
all missing System, Company, LAN, HBA, Video or Device information.
5b2 Click OK to close the Exception Information window.
5b3 Repeat for each driver ERROR:...missing... message.
6 Once all missing hardware has been added, click OK in the Product & Report Information window.
2.11.5 Saving the Test Project

1 Click on Save (at the top of the screen) to save the project.
2 Begin testing the system now according to the requirements for the test project. Follow the testing instructions in
the next section for the testing that you wish to perform. Run the tests in the order listed in this document.
During testing, TestConsole may prompt the tester for IP addresses, usernames, passwords, and user directory
context for the SUT. We have not documented all on screen prompts for each individual test. The answers to the on
screen questions should be obvious. If your DS contract includes an assigned SUSE engineer, you may contact
them for additional assistance.
61 Linux Test Suite

2.12 Test Results Definitions
Many of the tests in this section have 3 possible testing outcomes, pass, fail and pass w/warning. Below is an
explanation of the possible outcomes.
Pass test result - indicates that the tested configuration has completely passed the testing requirements.
PASS w/WARNING test result - indicates that the tested configuration has passed the testing requirements but may
have configuration issues which are in question. A PASS w/WARNING test result will need to be reviewed by a
SUSE engineer when the test results are submitted. If there were warning messages on the SUT, review these
messages with regards to your hardware.
Fail test result - indicates that the tested configuration has failed the testing requirements. There are many possible
reasons. This may be due to improper configuration or steps missed during testing.
2.13 Memory Persistence Test

Test Overview: This test will test the ability of the system's persistent memory to retain data after power off.
This test will only appear in the SLES projects.
1 Open a terminal.
2 In the terminal type ls /dev/pmem* <Enter>.
3 For each pmem device found, do the following (where X is a number):
3aType mkfs.xfs /dev/pmemX <Enter>
3bType mkdir -p /media/tc/memX <Enter>
3c Edit /etc/fstab file
3d Append the following line to the fstab file:
3e /dev/pmemX /media/tc/memX xfs dax 2 2
3f Save the /etc/fstab file and exit the editor
3g Type mount -a <Enter>
4 Double-click Memory Persistence Test in the TestConsole project for the SUT.
5 Follow the on screen instructions in the new console window that appears on the TC.
2.14 Kdump Test

Test Overview: This test will need between 5 GB and the equivalent to the amount of RAM in the system of free
disk space. The amount of free disk space needed depends on the amount of RAM in the system. SLED will need
more space on the / (root) then there is RAM for the test to properly run.
Test Objective: Verify that the OS and hardware can correctly perform a kernel crash dump (kdump).
_________________________________________________________________________________________
Note: Kdump is not supported on secure boot systems (when secure boot is enabled).
_________________________________________________________________________________________
62 Linux Test Suite

1 Double-click the Kdump Test in the TestConsole project for the SUT. Follow the on screen instructions on TC.
The onscreen instructions will direct the tester. A reboot may occur multiple times to perform and complete the
kdump test.
2.15 Serial Port Test Setup

Test Overview: This test is only required for systems with serial ports. This test is not part of the Xen or KVM
testing. This test is run independently from all other tests.
Test Objective: Verify that the Serial Port functions in the system.
________________________________________________________________________________________
192.168.101.255. These IP addresses are used in the Serial Port Test.
________________________________________________________________________________________
1 Connect the SUT serial port 1 and TC serial port 1 using a serial crossover cable or a serial null modem cable.
___________________________________________________________________________________________
Note: Com port 1 must = ttyS0 and have a speed setting of 115,200. We have had success using settings 3f8 and
IRQ4.
___________________________________________________________________________________________
2 Double-click Enable Serial Port 1 Test in the TestConsole project for the SUT.
3 Double-click the Serial Port 1 Test to begin the test.
_________________________________________________________________________________________
Note: If the serial port test is experiencing problems, then please refer the the serial port debug section of the
troubleshooting part of this document.
_________________________________________________________________________________________
2.16 Video Test

Test Objective: Verify that the display sleep functionality works on the system.
1 Double-click Video Test in the TestConsole project for the SUT.

2.17 Touchscreen Test

______________________________________________________________________________________________
IMPORTANT: Run this test only if you are performing a SLED certification. You do not need to run this test if you
are certifying with SLES.
______________________________________________________________________________________________
Test Objective: Verify that the touchscreen functions correctly with the OS.
1 Double-click Touchscreen Test in the TestConsole project for the SUT.
63 Linux Test Suite

2 Follow the on screen instructions in the new console window that appears on the SUT.
_____________________________________________________________________________________________
Note: If the test results returns an untested result then run the test again before any other test. This includes the test
not appearing to run.
_____________________________________________________________________________________________
2.18 Speaker Test

______________________________________________________________________________________________
______________________________________________________________________________________________
Test Overview: This test is required for systems which support audio output or which have built in speakers.
Test Objective: Verify that the sound card and speakers are compatible with the OS.
1 Double-click the Speaker Test in the TestConsole project for the SUT.
2.19 Microphone Test

______________________________________________________________________________________________
______________________________________________________________________________________________
Test Objective: Verify that the sound card and the usage of a microphone are compatible with the OS.
1 Double-click the Microphone Test in the TestConsole project for the SUT.
2.20 Volume Keys Test

______________________________________________________________________________________________
______________________________________________________________________________________________
Test Overview: This test is required for systems with built in volume control keys on the keyboard.
Test Objective: Verify that the volume keys are compatible with the OS.
1 Double-click the Volume Keys Test in the TestConsole project for the SUT.
64 Linux Test Suite

2.21 External Mouse Test
_____________________________________________________________________________________________
IMPORTANT: Run this test only if you are performing a SLED certification on a laptop/notebook system. You do
not need to run this test if you are certifying with SLES.
_____________________________________________________________________________________________
Test Overview: This test is required for systems which are able to have an external secondary USB mouse. If the
SUT does not have the ability to plug in an additional mouse, skip to the next test.
Test Objective: Verify that the OS can properly detect and use an external mouse on the system.
1 Double-click the External Mouse Test in the TestConsole project for the SUT.
2.22 External Keyboard Test

_____________________________________________________________________________________________
_____________________________________________________________________________________________
Test Overview: This test is required for systems that can use a secondary external keyboard (USB). If the SUT does
not have a way to plug in an additional keyboard (in addition to the built in keyboard), skip to the next test.
Test Objective: Verify that the OS can properly detect and use an external keyboard with the system.
1 Double-click the External Keyboard Test in the TestConsole project for the SUT.
2.23 External Monitor Test

_____________________________________________________________________________________________
_____________________________________________________________________________________________
Test Objective: Verify that the external monitor functions correctly with the OS. Start the test with no external
monitor connected.
1 Double-click External Monitor Test in the TestConsole project for the SUT.
__________________________________________________________________________________________
Note: If the test returns an untested result then run the test again before any other test. This includes the test not
appearing to run. The SUT and TC may need to be rebooted if the test will not complete.
__________________________________________________________________________________________
65 Linux Test Suite

2.24 Battery Test
______________________________________________________________________________________________
______________________________________________________________________________________________
Test Overview: This test is required for systems that can be powered by a battery (not an external UPS). The battery
must be fully charged prior to starting this test. If the SUT does not have a battery, skip to the next test. This test
must pass in order for power management to display yes on the bulletin. For more information about power
management requirements on a bulletin, please see the Yes Certified System Test Kit Policy document.
Test Objective: Verify that the OS can properly monitor the usage of the battery on the system.
1 Double-click the Battery Test in the TestConsole project for the SUT.
2.25 Power Management Tests

Test Overview: The power management tests will vary depending on the project chosen for the testing. All possible
Power Management Tests are listed in this section. For more information about power management requirements on a
bulletin, please see the Yes Certified System Test Kit Policy document.
2.25.1 Hibernate Test

____________________________________________________________________________________________
IMPORTANT: Run this test only if performing a SLED (latest support pack) certification. This test is optional for
SLES.
____________________________________________________________________________________________
Test Overview: This test must pass in order for power management to display yes on the SLED bulletin. For more
information about power management requirements on a bulletin, please see the Yes Certified System Test Kit Policy
document.
Test Objective: Verify that the OS can correctly put the machine into and recover from hibernation mode.
1 Double-click the Hibernate Test in the TestConsole project for the SUT.
2.25.2 Sleep Test

____________________________________________________________________________________________
IMPORTANT: Run this test only if performing a SLED certification. This test is optional for SLES.
____________________________________________________________________________________________
Test Overview: This test must pass in order for power management to display yes on the SLED bulletin.
66 Linux Test Suite

Test Objective: Verify that the OS can correctly put the machine into and recover from sleep mode.
1 Double-click the Sleep Test in the TestConsole project for the SUT.
2.25.3 CPU Frequency Test

______________________________________________________________________________________________
IMPORTANT: Ensure that the Auto Frequency (different vendors have different names for this) changing is enabled
in the system setup. This test may take more than 10 minutes depending on the number of CPU cores in the system.
______________________________________________________________________________________________
Test Overview: This is a fully automated test, there will not be any user interaction required. This test must pass in
order for power management to display yes on the SLED bulletin. For more information about power management
requirements on a bulletin, please see the Yes Certified System Test Kit Policy document.
Test Objective: Verify that the OS can change and monitor CPUs that support multiple frequencies.
1 Double-click the CPU Frequency Test in the TestConsole project for the SUT.
2.25.4 Fan Thermal Test

______________________________________________________________________________________________
______________________________________________________________________________________________
Test Overview: This test is fully automated, there will not be any user interaction required.
Test Objective: Verify that the OS can properly monitor the change of temperature and fan states (on/off) on the SUT.
1 Double-click the Fan Thermal Test in the TestConsole project for the SUT.
2.25.5 Throttling Test

______________________________________________________________________________________________
______________________________________________________________________________________________
Test Overview: This test is fully automated, there will not be any user interaction required.
Test Objective: Verify that the OS can properly change the throttling settings on the CPUs (if supported).
1 Double-click the Throttling Test in the TestConsole project for the SUT.
2.25.6 Brightness Test

_____________________________________________________________________________________________
67 Linux Test Suite

_____________________________________________________________________________________________
document.
Test Objective: Verify that the setting of the display brightness is compatible with the OS.
1 Double-click Brightness Test in the TestConsole project for the SUT.

___________________________________________________________________________________________
Note: The brightness test may report a PASS w/WARNING result. This means that the automated portion of the
brightness test failed and that the brightness cannot be controlled through the OS.
___________________________________________________________________________________________
__________________________________________________________________________________________
appearing to run.
__________________________________________________________________________________________
2.25.7 Brightness Keys Test

______________________________________________________________________________________________
______________________________________________________________________________________________
document.
Test Objective: Verify that the keyboard can be used to set the screen brightness.
1 Double-click Brightness Keys Test in the TestConsole project for the SUT.
2.25.8 Lid Close Test

______________________________________________________________________________________________
______________________________________________________________________________________________
document.
Test Objective: Verify that closing and opening the laptop lid is compatible with the OS.
68 Linux Test Suite

1 Double-click Lid Close Test in the TestConsole project for the SUT.
___________________________________________________________________________________________
appearing to run.
___________________________________________________________________________________________
2.26 Verify Setup Tests

Test Overview: The Verify tests and the other tests in this section are for the pre-stress test assurance. These tests will
verify that the hardware is configured correctly and that the stress tests are ready to be run.
2.26.1 Verify Setup - NIC 1

Test Objective: Verify that the NIC configuration is correct including LAN speeds and IP addresses. This test must
pass before starting the stress tests.
1 Ensure that the IP address for the NIC is correct.

• SUT NIC 1 (default) IP address 10.1.1.1
• TC NIC 1 (default) IP address 10.1.1.2
2 Double-click Verify Setup – NIC 1 in the TestConsole project for the SUT.
3 Test explanations:
The NIC verify test will take a few minutes to complete.
If the test fails, troubleshoot the NIC setup by reviewing the configuration information in Section 2.1,
“Configuring the Hardware” and Section 2.2, “Setting Up TC” to ensure that the hardware is set up correctly.
A “PASS w/WARNING” result may indicate that the SUT NIC speed is not detectable with ethtool. If the SUT
NIC speed is not detectable with ethtool then the tests are unable to verify that the network configuration is setup
correctly.
2.26.2 Verify Setup - NIC 2 through 16

Test Overview: This test is required for all systems with 2 or more wired NICs. All NIC ports, up to 16, are required
to be tested. The verify setup NIC test will test up to 16 NIC ports individually. This test is required to be run prior to
the stress tests. All NIC IP addresses, including any needed Alias IP addresses must be correctly set up for the stress
testing. At this time please review all IP address information for accuracy. This test must pass for all NIC ports before
starting the stress tests.
Test Objective: Verify that the NIC set configuration is correct including speeds and IP addresses.
1 Ensure that the IP address for each NIC is correct.

69 Linux Test Suite

• TC NIC 3 (default) IP address 10.1.3.2 and so on
2 Double-click Verify Setup – NIC x (x=2 to 16) in the TestConsole project for the SUT.
3 If Verify Setup was clicked, then click Continue in the Verify Run window.
4 The NIC verify test will take a few minutes to complete. Test results explanations:
If the test fails, troubleshoot the NIC setup by reviewing the configuration information in Section 2.1,
“Configuring the Hardware” and Section 2.2, “Setting Up TC” to ensure that the hardware is set up correctly.
A “PASS w/WARNING” result may indicate that the SUT NIC speed is not detectable with ethtool. Then the tests
are unable to verify that the network configuration is setup correctly.
5 Repeat steps 1 through 4 for each NIC, upto NIC 16.
2.26.3 Verify Setup – Wireless NIC

Test Overview: This test is required for all SLED systems with a wireless NIC. This test is required to be run prior to
the stress tests. All NIC IP addresses must be correctly set up for the stress testing. At this time please review all IP
address information for accuracy.
Test Objective: Verify that the Wireless NIC configuration is correct including speeds and IP addresses.
______________________________________________________________________________________________
Note: When testing a SUT workstation, desktop or laptop that contains a wired and wireless NIC, the wired NIC
configuration should have been used for testing up to this point. Now the wireless NIC should be configured for the
stress testing. If the wireless adapter was previously used, then removing the Ethernet cable may switch to the
wireless NIC automatically.
______________________________________________________________________________________________
Enable the Wireless NIC.
1 Remove wired Ethernet cable from the SUT Ethernet port.
2 For a SLED 12 SP3 SUT do the following:
2a Click on Applications in the lower left corner.
2b Mouse over System Tools.
2c Click on Network Tools on the right.
2d Click on the Devices tab.
2e Choose the wireless NIC to be configured by clicking on the Network device drop down, then click on the
Wireless Interface.
2f Click on Configure.
2g Click on the Wireless Connection, then click Edit.
2g1 If the Wireless connection is not listed click Add then scroll down and select Wi-Fi. Click create. Enter the
SSID.
2h Click on the IPv4 Settings tab.
2i Click on the Method drop down, choose Manual.
70 Linux Test Suite

2j Click Add next to the Address Table.
2k Type in the static IP address (i.e. 10.1.1.1), then press <Enter>.
2l Type in the Netmask (i.e. 255.255.255.0), then press <Enter>.
2m Click on Save.
2n Click Close in the Network Connections window.
2o Close the Devices-Network Tools window by clicking the 'x' in the upper right corner.
______________________________________________________________________________________
Note: The IP address changes will not be reflected in the Devices-Network Tools window until the SUT is
rebooted.
______________________________________________________________________________________
2p Reboot the SUT for the IP address to take effect on the wireless lan (wlan) adapter. Then login as root.
2q After the SUT reboots the wireless NIC may need to be turned on. To turn on the wireless NIC click on the
speaker in the display bar on the lower right. Click on the wireless then choose Turn On, if it's not already on.
2r Select the Wi-Fi Network which the TC is connect to. Click on the speaker in the display bar on the lower
right. Click on Wi-Fi Not Connected. Click on Select Network. Click on the Network which TC is on. Click on
Connect. Enter the Network password. Click on Connect.
2s Open a terminal then type ifconfig <Enter>. The IP address information will be displayed. If the IP address for
the wlan is incorrect then repeat the steps in 2 above.
3 Double-click Verify Setup - Wireless NIC in the TestConsole project for the SUT.
4 If prompted click Continue in the Verify Run window.
The NIC verify test will take a few minutes to complete. If the test fails, troubleshoot the NIC setup by
reviewing the configuration information in Section 2.1,“Configuring the Hardware” and Section 2.2, “Setting Up
TC” to ensure that the hardware is set up correctly. A “PASS w/WARNING” result may indicate that the SUT NIC
speed is not detectable with ethtool. If the SUT NIC speed is not detectable with ethtool then the tests are unable to
verify that the network configuration is setup correctly.
2.26.4 Verify Time Sync Setup

Test Objective: Verify that the time is correctly synced between the SUT and the TC. This test must pass before
starting the stress tests.
1 Ensure that the IP address for the adapter is correct.

• All VM IP addresses
2 The following needs to be done on SUT and on each VM.

2a On SUT open a Terminal
2b Type ntpq -p<Enter>
2c The onscreen output should be as follows:
remote refid st t when poll reach delay offset jitter
71 Linux Test Suite

==============================================================================
*10.1.1.2 LOCAL(0) 11 u 343 1024 377 2.109 -1.076 0.891
Interpretation of relative output: “remote” needs to be the IP address of TC. The “*” in front of the remote IP
address and “reach” of 377 means that everything is synced up correctly.
2d If the time is not synchronized then check the configuration and the IP addresses. After boot, the time
synchronization can take up to 30 minutes. The average time synchronization is about 10 minutes. Close the
ntpq window once the time is synced.
3 Double-click Verify Time Sync Setup in the TestConsole project for the SUT. If the test fails then follow the
onscreen instructions. If the onscreen instructions do not solve the problem then see the Time Sync troubleshooting
section of this document.
2.27 Specialty Tests

Test Overview: This section of tests are used for certain situations. The tests will only appear in the test project
when applicable. Each will be explained in it's own section.
2.27.1 NIC 1 Reduced Test

Test Overview: This test is required for a SLED SUT configured with a wired NIC and a wireless NIC. The NIC 1
Reduced Test is automatically enabled when the wireless NIC test is enabled. This is a 2 hour NIC test.
Test Objective: Verify that the NIC and driver function well with the OS.
1 Ensure that the IP address for the NIC is correct.

2 Double-click NIC 1 Reduced Test in the TestConsole project for the SUT. The test will begin.
2.27.2 Verify PCI Pass-Through/SR-IOV Setup

Test Overview: This test is required for SLES versions after SLES 11 SP4 using KVM or using Xen configurations.
This test is required to be run and pass prior to starting the stress tests. At this time please review all IP address
information for accuracy.
Test Objective: Determine if the PCI Pass-Through or SR-IOV NIC configuration is working.
1 If the NIC is PCI Pass-Through or SR-IOV capable then configure it before starting this test. Most new NICs are
PCI Pass-Through capable. See Configuring KVM for Network PCI Pass-Through or see Configuring KVM for SR-
IOV or see Configuring Xen for Network PCI Pass-Through or see Configuring Xen for SR-IOV in this document for
more information.
2 Double-click Verify PCI Pass-Through/SR-IOV Setup Test.

3 Test results explanations:
A test failure will occur when the NIC is:
- not PCI Pass-Through capable and not SR-IOV capable (which is okay for Yes Certification).
72 Linux Test Suite

- not configured correctly (which will prevent Yes Certification).
2.27.3 CPU Over-Commit Setup

Test Overview: This test is required for SLES versions after SLES 11 SP4 using KVM or using Xen configurations.
This test is required to be run and pass prior to starting the stress tests.
Test Objective: Determine if the CPU over commit was set up correctly as defined in this Test Kit documentation.
1 Double-click CPU Over-commit Setup Test.

2 Test results explanations: A test failure will occur when the CPU is not over-committed correctly.
73 Linux Test Suite

2.28 Optical Device Tests Overview
Test Overview: The Optical Device Tests are always required. The Optical Device Tests will detect and test all optical
devices which are directly connected to the SUT. If the SUT does not have an optical device then the test will return
the test result of “NOT APPLICABLE”. Virtual optical devices (Virtual DVD, Virtual CD, etc) will not be tested but
will cause a “PASS w/WARNING” result. Optical media tests will also be performed on a Xen Guest and on a KVM
Guest.
Test Objective: Verifies that the optical devices function correctly with the other devices in the system.
Yes Certification requires that the most capable functionality of each optical device be tested. The most capable
function is always write capability.
Optional:
1 The capabilities of the optical device can be determined before testing the devices.
2 Determine the capabilities of the optical device by looking up the specs on the device.
3 Place the appropriate media into each optical device. See table 2-2 below to determine which media to place into
the optical media device.
____________________________________________________________________________________________
Note: If a SUSE Hardware Detection pop up appears, place a check mark next to Do not ask again and click No or
Cancel to not open the application.
____________________________________________________________________________________________
3a During the testing the test will prompt on SUT if the wrong media is in the optical media device.
3b Incorrect media will result in a test failure within several minutes.
4 If the tests fails due to incorrect media, simply replace the media with the correct media then restart the optical
media test.
Table 2-2 CD-ROM/DVD Test Matrix

________________________________________________________________________________________
Drive Features Media to place into drive

________________________________________________________________________________________
CD Test with CD media with 600MB or more of data on it
CD-RW Test with blank CD-RW media
CD-R Test with blank CD-R media
DVD Test with DVD media with 3GB or more of data on it
DVD-RW Test with blank DVD-RW or DVD-R media
DVD+RW Test with blank DVD+RW or DVD+R media
DVD-R Test with blank DVD-R media
DVD+R Test with blank DVD+R media
No Features line found See /proc/sys/dev/cdrom/info for features.
Blu-ray Not supported on SLE. Test a DVD instead.
____________________________________________________________________________________
___________________________________________________________________________________________
Note: Please verify that the write speed of the CD or DVD writable media matches the optical drive write speed.
If the write speed of the media is slower than the write speed of the optical drive, the test may fail.
___________________________________________________________________________________________
74 Linux Test Suite

2.28.1 Optical Verify/Write Test
Test Overview: This test will exercise the optical devices write capability. If the SUT does not have an optical device
with write capability then the test will return the test result of “NOT APPLICABLE”. Blu-ray is not supported in
SLE, please use a DVD for testing Blu-ray devices. This test is required to be run prior to the stress tests on all
systems. Do not remove the written media after the test has completed. Once the test has completed the written
media will be used for the Optical Read Test during the 12 hour stress tests.
Test Objective: Verify that the optical write capability functions correctly with the OS.
1 Determine if the optical device supports auto-trayclose.

1a On SUT type eject <Enter> at the command line to eject the CD/DVD.
1b On SUT type eject --trayclose <Enter> at the command line to close the tray. If the tray closes and the command
does not return an error then it is supported.
_________________________________________________________________________________________
IMPORTANT: If the optical device does not support auto-tray close then the tester will need to manually close
the tray during testing.
_________________________________________________________________________________________
2 On the SUT place a blank writable (or rewritable) media that supports the maximum write speed of the drive into
each optical media device. If prompted, Cancel at the choose what application to open prompt.
3 Double-click the Optical Verify/Write Test. The Test will begin. Messages generated during this test will pop up on
the TC.
2.29 Stress Tests

Test Overview: As each test is set up, the actual test will be added into a folder called Stress Tests in the Project
Contents pane. The stress tests will be started at the same time and run together to stress the overall system more
efficiently and reduce testing time. After all testing is complete the Get Test Logs Test is the final test. Do not run the
Get Test Logs Test until all testing is completed.
2.29.1 Persistent Memory Test

Test Objective: Test compatibility of the systems persistent memory. Example: NVDIMM. Returns N/A if the test
does not apply. This test does not require any setup.
2.29.2 Memory/CPU Test Setup

Test Objective: Verify that the CPU's and memory function correctly under stress for an extended amount of time.
This test does not require any setup.
2.29.3 Hard Disk/RAID Test Setup

Test Overview: The Hard Disk/RAID device test is always required. The Hard Disk/RAID test will detect and test all
Hard Disks and/or hardware RAID devices which have a mountable partition. The hardware RAID testing is for
hardware RAID only, it is not intended for testing software RAID. This test will exercise SCSI, SATA, eSATA, SAS,
75 Linux Test Suite

IDE and Fibre Optic connected devices. If this test is for a virtual machine, please remove the virtual DVD or it will
be tested as a hard disk. If the SUT does not have a Hard Disk/RAID device then the test will return the test result of
“NOT APPLICABLE”.
Test Objective: Verify that the Hard Disk or RAID and driver functions correctly with the system.
1 If you want to list an eSATA port on the bulletin then connect the eSATA device to the eSATA port. The eSATA
device must be tested during the certification tests. See Section 2.28.7 “USB Test Setup” instructions to format
external drives.
2 This test is enabled by default and will run with the stress tests.
2.29.4 NIC Test

Test Objective: Verify that the NICs function correctly under stress for an extended amount of time. The Verify
Setup – NIC tests are required to be run and pass prior to starting this test. If SUT has a wireless NIC, then the
Wireless NIC Test will be displayed in place of the NIC Test.
If the test fails, troubleshoot the NIC setup by reviewing the configuration information in Section 2.1, “Configuring
the Hardware” and Section 2.2, “Setting Up TC” to ensure that the hardware is set up correctly. A “PASS
/WARNING” result may indicate that the SUT NIC speed is not detectable with ethtool. If the SUT NIC speed is not
detectable with ethtool then the tests are unable to verify that the network configuration is setup correctly.
2.29.5 Time Sync Test Setup

Test Objective: Verify that the time remains synced between the SUT and the TC. This test does not require any
setup.
2.29.6 Floppy Test Setup

Test Overview: This test is required for systems which have a floppy disk drive. If the SUT does not have a
floppy disk drive, go to the next test.
Test Objective: Verifies that the Floppy Disk functions correctly with the other devices in the system.
1 Place a blank floppy disk into the SUT floppy drive.

_______________________________________________________________
WARNING: The contents of the floppy disk which you insert will be erased.
_______________________________________________________________
2 If testing a USB floppy drive, attach the USB floppy drive to SUT.
3 Double-click Enable Floppy Test in the TestConsole project for the SUT.
April 2007
2.29.7 Optical Read Test

Test Overview: This test is required to be run on all systems. If the SUT does not have any optical devices then the
test will return a test result of “NOT APPLICABLE”. The section below describes the procedure for preparing to run
the optical read test on a KVM guest or a Xen guest. Blu-ray is not supported in SLE, please use a DVD for testing in
Blu-ray devices. This test will exercise the read capabilities of all optical devices attached to the SUT. Do not remove
76 Linux Test Suite

any written media created from the Optical Verify/Write Test, it will be used during this Optical read test.
Test Objective: Verifies that the Optical devices function correctly with the other devices in the system. For Xen this
test works on the second installed Xen VM. The second Xen VM must be a fully virtualized (FV) SLES guest.
1 This test is enabled by default and will run with the stress tests. Messages generated during this test will pop up on
the TC.
Instructions for a KVM guest and a FV Xen guest which have an optical media device in SUT:
1 Ensure that the KVM guest or a FV Xen guest is installed.
2 Ensure that the Test Kit is installed on the KVM guest or the FV Xen guest.
3 Insert the optical media into the optical media device.
4 Using the VM manager, shut down a KVM guest or a Xen guest.
5 Click on View → Details on the KVM Guest or Xen Guest which is shutdown.
6 Click on the Add Hardware button.
7 Ensure that storage is selected in the left hardware screen listing.
8 Click on the radio button next to “Select Managed or Other existing Storage”
9 In the text field next to the browse button type the following /dev/sr0.
10 Click on the drop down next to the device type and select IDE cdrom.
11 Click Finish.
12 The IDE cdrom or the Xen cdrom will be displayed in the left window.
13 Click View → Console.
14 Click the power on button for the KVM guest or the Xen guest. It appears as a right pointing triangle.
15 The system is now prepared to run the optical read test during the stress tests.
2.29.8 USB Test Setup

Test Overview: The USB device test is always required. If the SUT does not have a USB controller then the test will
return the test result of “NOT APPLICABLE”. The USB test will detect and test all USB devices which have a
mountable partition. This test is intended for exercising 2 USB storage devices connected to the SUT. If the SUT has
2 USB ports then plug a USB device into each port.
When a USB keyboard or a USB mouse is using one of the 2 USB ports then an external USB hub is required to
ensure that 2 USB storage devices are tested. A USB Keyboard, or a USB Mouse and USB hard drive can be plugged
into the USB hub and the other USB hard drive is plugged into the other USB port. If the SUT has only 1 USB port
then only 1 USB storage device must be tested. The volume name on the USB storage device must not have any
spaces in the name.
Test Objective: Verifies that the USB port functions correctly with the other devices in the system.
1 Connect the USB storage devices to the SUT. If there are USB ports on the front and the back of the SUT, then plug
one USB storage device (or flash drive/thumb drive) into the front USB port and the other USB storage device (or
flash drive/thumb drive) into a back USB port. If prompted to open a new hard disk, click No.
2 The USB storage device needs to be partitioned for Linux. To do so open the System Partitioner to configure the
USB storage device. If the USB storage device has already been partitioned using the procedure below, then you do
77 Linux Test Suite

not need to format the USB storage device again. The USB storage device only needs to be partitioned once using
the below procedure.
2a At a terminal prompt, type yast2 disk<Enter>.
2b Click Yes at the warning.
3 Double click the new USB storage device (e.g., sdb or sdc).
4 Remove existing partitions on the USB storage device.
4a Click Delete.
4b If prompted click Continue at the warning screen about unmounting the drive.
4c Click Yes to really delete the partition.
4d If prompted click Continue to unmount the drive.
5 Create a new partition on the USB storage device.
5a Click Add.
5b Click the Primary Partition radio button then click Next.
5c Click Next, for the default partition size.
5d On SLE 11 ensure that the Do not mount partition radio button is selected, then click Finish.
5e Choose ext3, then click Next.
5f Click Finish to format the USB storage device.
5f On SLES 12 click Next on the Expert Partitioner screen. Click Finish on the next screen.
6 Mount the USB storage device.
6a Unplug the USB storage device, wait 20 seconds and then plug it back in. This should cause it to mount under
/media.
2.29.9 FireWire Test Setup

Test Overview: The FireWire device test is always required. If the SUT does not have a FireWire controller then the
test will return the test result of “NOT APPLICABLE”. The FireWire test will detect and test all FireWire storage
devices which have a mountable partition. This test is intended for exercising 2 FireWire storage devices. If the SUT
has 2 FireWire ports then plug a FireWire storage device into each port. If SUT has only 1 FireWire port then the 2
FireWire storage devices must be connected (chained) together.
If a USB floppy drive is also being tested, you may encounter Firewire test failures. If the firewire test fails under
these conditions then we recommend running the stress tests without the Floppy disk test. In this situation run the
floppy disk test separately alone.
Test Objective: Verify that the FireWire port functions correctly with the other devices in the system.
1 Connect the 2 FireWire storage devices to the SUT. If there are FireWire ports on the front and back of the system,
plug one fireWire storage device into a front port and the other FireWire storage device into a back port.
2 The FireWire storage device needs to be partitioned for Linux. To do so open the System Partitioner to configure
the FireWire storage device.
2a At a terminal prompt, type yast2 disk<Enter>.
78 Linux Test Suite

2b Click Yes at the warning.
3 Double click the new FireWire storage device (e.g., sdb or sdc).
4 Remove existing partitions on the FireWire storage device.
4a Click Delete.
4b Click Continue if prompted to unmount the FireWire drive.
4c Click Yes to really delete the partition.
5 Create a new partition on the FireWire storage device.
5a Click Add.
5b Click the primary partition radio button, then click Next.
5c Click Next in the new partition size screen.
5c Choose ext3, then click Next in the Add partition screen.
5d Click Finish.
5e Click Next in the expert partitioner screen.
5e Click Finish in the summary screen.
5f Repeat steps 3 - 5e for the 2nd FireWire storage device.
6 Mount the USB storage device.
6a Unplug the USB storage device, wait 20 seconds and then plug it back in. This should cause it to mount under
/media.
2.29.10 Error Check Test

Test Objective: Verify that there were no system problems during the stress tests. This test does not require any
setup.
2.29.11 Starting the Stress Tests

Test Objective: Verify that all system devices function correctly together in a high load situation for an extended
period of time. All tests in the Stress Tests folder must be started within 1 hour of the first Stress Test which is started,
or the Verify Stress Tests will fail. If all Stress Tests are not started within 1 hour of each other, then all Stress Tests
should be canceled. After the Stress Tests are canceled and no longer listed in the testing run queue window, the 12
hour Stress Tests should be completely restarted. All Stress Tests must run for a minimum of 11 hours together, or 3
hours together during the reduced testing project.
1 Double-click the Stress Tests folder.

2 Click “Continue” in response to the “Verify run” pop-up window. This will start all of the stress tests which were
set up.
3 Wait 15 minutes and check see if any of the tests have failed.
4 If any tests have failed within the first hour:
4a Correct the problem (see Appendix A, “Troubleshooting”).
79 Linux Test Suite

4b Restart the failing test within the first hour by double clicking on the failed test and then go back to step 3.
2.30 Verify Stress Tests

Test Overview: This test is required for all systems. This test will ensure that all stress tests were run as expected and
according to the testing policy. For testing policy information see section 1.2 of this documentation.
1 After the Stress Tests have completed double-click the Verify Stress Test to begin this test.
2.31 Evaluating the Results of the Stress Tests

1 After all the tests have completed, check to see if any tests have failed.
2 If a test has failed, check the test configuration setup then return to the Section entitled, “Starting the Stress Tests”.
All tests must be run in parallel as defined in the section entitled, “Stress Tests”.
2.32 Post-Testing Cleanup

1 If USB storage devices were used during testing, then safely remove them from the SUT.
2 If CD/DVD media was used during testing, then safely remove it from the SUT.
3 If a floppy diskette was used during testing then remove it from the SUT.
4 If FireWire storage devices were used during the testing, then safely remove them from the SUT.
2.33 Get Test Logs Test

Test Overview: This test is required for all systems. This test will gather all test logs in preparation for the creation of
the test results submission file.
___________________________________________________________________________________________
Note: For Xen or KVM certification, run each individual “Get VMx (x=3,2,1) test logs” until completion before
starting the “Get SUT test logs”.
___________________________________________________________________________________________
1 Double-click Get Test Logs in the TestConsole project for the SUT. This test can take time to complete. We have
seen systems with 5 TB of RAM take 2 hours to complete this test.
_____________________________________________________________________________________________
IMPORTANT: Do not run the Get Test Logs Test until all testing is completed. Do not shut down any VM Guests
until after completing the next section entitled Submitting Test Results.
_____________________________________________________________________________________________
2 If prompted answer the on screen questions.
3 Continue to section 2.33 “Submitting Test Results”.
80 Linux Test Suite

2.34 Creating the Bulletin Submission File
Overview: We refer to the test results .zip file as the bulletin submission file. The bulletin submission file is used to
create the Yes Certification Bulletin in the SUSE Bulletin System (SBS). The steps in this section will create the
bulletin submission (.zip) file which you will read into SBS to create the Yes Certification Bulletin.
1 Open the project file. If the project file is already opened, skip to step 2.
__________________________________________________________________________________________
IMPORTANT: If the project file is already open and you have just completed the tests, save the project before
creating the bulletin submission (.zip) file.
__________________________________________________________________________________________
1a Click the TestConsole icon on the desktop
1b Click Project > Open Test Project > Existing.
1c Select the appropriate project.
1d Click Select to open the project.
2 Create the bulletin submission (.zip) file.
2a Click Edit Product/Report.
2b Click Report.
_______________________________________________________________________________
IMPORTANT: If the Report Error window appears, continue to step 3. If not, proceed to step 4.
_______________________________________________________________________________
3 Report errors.
3a Click on the x in the upper right corner of the Report Error window to close the window.
3b Click Verify.
3c Click an exception in the scroll window.
3d Click Edit Explanation.
3e Enter the explanation.
3f Click OK in the explain exception window.
3g Repeat steps c through f until all unresolved exceptions are explained.
3h Click OK in the Exception Information window.
3i Click Report. If the screen appears stuck then click on the terminal screen at the bottom then click inside the
screen.
4 Complete the creation of bulletin submission (.zip) file.
4a Keep the the existing project filename. Do not change the filename.
4b Click Save to generate the bulletin submission (.zip) file.
4c Click View Report Summary to view the reported information in a browser.
4d Close the browser window.
4e Click OK to exit the Product and Report Information window.
5 Copy the bulletin submission (.zip) file from the /opt/suse/testKits/system/results directory to a USB Flash drive or
CD or Network.
81 Linux Test Suite

5a For example: if copying the bulletin submission (.zip) file to a USB thumb drive, at a terminal prompt on TC
type: cp <bulletin submission (.zip) file> /media/usb<Tab> <Enter>.
6 Follow the instructions in section F to read the bulletin submission (.zip) file into the SUSE Bulletin System (SBS).
If you cannot access SBS, then contact your SUSE Developer Services contact for SBS access.
7 For the Xen Host, now that the base cert testing is completed, goto to Chapter 4.1, “Installing a Xen Virtual
Machine” to set up the Xen virtual machines.
8 For the KVM Host, now that the base cert testing is completed, goto to Chapter 5.1, “Configuring the KVM Server”
to set up the kernel based virtual machines.
82 Linux Test Suite

3
Manually Installing SLED 12
This section covers the following topics for manual OS installations:
• Section 3.1, “Configuring the Hardware for SLED Testing”

• Section 3.2, “Setting Up TestConsole”
• Section 3.3, “Manually Installing SLED 12 SP3 on SUT”
• Section 3.4, “Manually Installing the Test Kit on the SLED 12 SP3 SUT”
• Section 3.5, “Starting the Tests”
3.1 Configuring the Hardware for SLED 12 SP3 Testing

Figure 3-1 Hardware Configuration for the SLED Testing
________________________________________________________________________________________
192.168.101.255. These IP addresses are used in the Serial Port Test.
________________________________________________________________________________________
Figure 3-2 Hardware Configuration for the Stress Tests with Wireless Adapter
83 Manually Installing SLED 12

______________________________________________________________________________________________
Note: If a wired and wireless adapter are to be included on a certification bulletin then both must be tested using the
SLED Workstation or SLED Laptop project. The wireless is tested during the stress test and the wired is tested
separately during a reduced 2 hour NIC test.
______________________________________________________________________________________________
3.2 Setting Up TestConsole

1 Install SLES 11 SP4 on TestConsole (see Section 2.2, “Setting Up TC”).
2 Complete the SLES 11 SP4 test kit installation (see Section 2.2.2, “Installing the Test Kit on TC”).
3.3 Manually Installing SLED 12 SP3 on SUT

The NICs in TC must match the highest speed NICs in the SUT.
1 Delete all existing partitions from all hard drives. Section “A.1.1 Removing the ELIO Boot Tables” has instructions
which will delete any and all existing partitions. For a DVD installation do the following, if this is a PXE manual
installation skip to step 4:

2 Boot the system to SUSE LINUX Enterprise Desktop 12 (latest support pack) from DVD.
3 Select Installation<Enter> (before the 20 second timeout expires).
For a PXE manual install start here:

4 If prompted click No to the Network is not configured...message in the Updating the installer screen.
5 Select the English (US) language and English (US) keyboard Layout.
6 Select I Agree to the License Terms, then click Next.
7 If prompted click Next in the Network Settings screen. The network will be set up in the next section during the
Test Kit installation on this SUT.
8 Click the Skip Registration radio button on the Registration screen.
8a Click OK at the registration warning prompt. Then click Next.
9 If prompted click Next in the Add On Product or Media Type or Installation Options screen.
10 The default manual SLED installation does not allocate enough space on / (root) to perform the kdump test, so the
partition needs to be changed.
10a Click “Edit Proposal Settings”.
10b Uncheck “Propose Separate Home Partition”.
10c Click OK.
10d Click Next.
11a Click on your region in the Region pull down menu on the left side or click on your time zone in the map.
11b Click on your time zone in the Time Zone pull down menu on the right side or click on your time zone in the
map.
12 Set the system clock to match the time of the other systems on your test rack.
12a Click the Other Settings button.
12b Change the Current time and Current date to be the same as the TC time and date.
12d Click the Next button to complete the setup of the Clock and Time Zone screen.
13a Click the Skip User Creation radio button on the Local User screen.
13b Click Next in the Local User screen.
14 Set the Password for the System Administrator user root.
14a Type suse in both fields for the System Administrator root user password.
14b Click Next.
14c Click Yes in The password is too simple message window.
15 Select the software to install on the system.
15a Select Installation Settings > software.
15b Click the Details button at the bottom left.

15c Select the software patterns.
Ensure that only the following patterns are checked with a green check mark or green check marks with 3
dots. Some black and white checks may need to be changed to green or left as black and white.
✔ GNOME Desktop Environment (Default) (choose both, if listed twice)

✔ X Window System
✔ Fonts
✔ Help and Support Documentation
✔ Laptop (if SUT is a laptop)
✔ AppArmor
✔ Desktop Base System
✔ 32-bit Runtime Environment
15d Click on the Search Tab.
15e In the Search box, type dmidecode, then click the Search button.
15f If unchecked, check the dmidecode package for installation.
15g In the Search box, type yast2-kdump, then click the Search button.
15h If unchecked, check the yast2-kdump package for installation.
15i In the Search box, type dvd+rw-tools, then click the Search button.
15j If unchecked, check the dvd+rw-tools package for installation.
15k In the Search box, type kdump then click the Search button.
15l If unchecked, check the kdump package for installation.
15m In the Search box, type mokutil, then click the Search button.
15n If unchecked, check the mokutil package for installation.
15o In the Search box, type mgetty, then click the Search button.
15p If unchecked, check the mgetty package for installation.
15q In the Search box, type sysstat, then click the Search button.
15r If unchecked, check the sysstat package for installation.
15s In the Search box, type makedumpfile, then click the Search button.
15t If unchecked, check the makedumpfile package for installation, then click Accept.
15u If prompted, click Accept in the Yast2 windows for the different software (flash-player-gnome,
gstreamer-0_10-fluendo-mp3, flash-player, gstreamer-fluendo-mp3, etc).
15v If prompted, click Continue to accept the Automatic Changes.

15w If prompted, click Continue in the Changed Packages window to accept the Unsupported Packages.
16 Disable the firewall by clicking on disable next to firewall will be enabled. The display will change to firewall
will be disabled.
17 Enable the SSH service by clicking on enable, located next to SSH service will be disabled. The display will

change to SSH service will be enabled.
18 If listed, enable an SSH port by clicking on open, located next to SSH port will be blocked. The display will
change to SSH port will be open.
19 Click Install to start the installation.
20 Click Install in the Confirm Installation window.
21 The file copying will begin. After the OS installation completes, the system will restart. After the restart, remove
the OS DVD from the SUT.
22 Proceed to Section 3.4 “Manually Installing the Test Kit on the SLED 12 SP3 SUT”.
3.4 Manually Installing the Test Kit on the SLED 12 SP3 SUT
1 Log in as root.
2 If a PXE install was used to install the OS onto the SUT, then the root password created by a PXE automatic install
will be suse.
3 Insert the current System Test Kit CD. The CD will automount. If the SUT does not have an optical media device
then a loop mount procedure can be used by following the steps below:
3d Type the following in a terminal window: /root/Desktop/sck/sck_install.sh <Enter>. Skip to Step 9 below.
4 If prompted, click on the x in the upper right corner in the CD-ROM prompt to close the CD window.
5 Open a terminal by right-clicking on the desktop, then click Open in Terminal.
6 Type /<mount point>/sck_install.sh <Enter>, Example: /run/media/root/CDROM/sck_install.sh.
7 When prompted remove the Test Kit DVD then replace it with the OS DVD. This must be the same OS DVD which
was used to install the OS onto the SUT.
8 Run the Test Kit script file as indicated in the onscreen message (example: /root/sck/sck_install.sh).
9 Choose the “SUT System” install, then press <Enter>. Example: 1 <Enter> for SUT.
10 When prompted, enter the IP address of TestConsole (default = 10.1.1.2) then press <Enter>.
12 Messages and prompts may occur as follows:
12a A Network Manager connection message may pop up on the right.
12b If prompted (in the Test Kit installation window) with instructions to start or stop a procedure, follow the
instructions. If the process does not stop/start, the issues will be resolved upon reboot in the end of this
section.
12c If prompted, enter the TestConsole IP address again (default = 10.1.1.2) then press <Enter>.

12d Press <Enter> in the Test Kit installation terminal window as prompted.
13 When prompted to “Enter a NIC number to modify...”, the NICs should already be configured by the test kit.
Press c to continue unless additional changes are needed. If the Wireless NIC is listed as “do not test” it's ok. The
wireless NIC will be configured later when starting the wireless NIC test.
15 Press <Enter> as prompted once the Test Kit installation has completed.
16 Close the terminal window by typing: exit <Enter>. This is important.
17 Right-click on the speaker in the bottom right of the Display panel.
18 Click on the round button which has the screw driver and the wrench inside.
19 Click Date and Time.
20 Select AM/PM in the drop down box next to Time Format.
21 Click on the x in the upper right corner to Close the window.
22 If a CD/DVD was used to install the testkit then remove the CD/DVD. If a USB storage device is plugged into the
SUT remove it. Reboot the SUT.
23 Verify this system has the same time setting as TestConsole (see Section A.4, “Time Synchronization,” for more
information).
24 Proceed to Section 3.5 “Staring the Tests”.
3.5 Starting the Tests

1 Begin at section Section 2.5, “Updating the Products.txt File” to begin Yes Certification testing.
en) 6 April 2007
88
4
Xen Virtual Machine Tests
Before Xen can be configured on the SUT, please follow the instructions in Section 2.3.1, “Installing
SLE on SUT through PXE” including Section 2.4, “Installing the Test Kit on the SUT”. The goal of this test is to
certify a Virtual Machine with maximum configuration (VMM guest) of RAM and available CPU's then to certify 3
different virtual machines on Xen simultaneously. After the VMM guest is tested it must be either re-configured to
become the VM1 guest or it should be shut down or deleted. If certifying with more than 3 VM's contact SUSE prior
to certification testing. We require that the hardware be certified with SLES 11 (latest support pack), SLES 12 SP3
only, prior to the Xen certifications.
We require Network PCI Pass-Through or SR-IOV to be tested on all SLES host versions after SLES 11 SP4 during
Yes Certification (if a LAN adapter in the SUT supports the functionality). A configuration Note must be added to all
Xen bulletins (for SLES host versions after SLES 11 SP4) for Network PCI Pass-Through or SR-IOV. Examples of
the configuration notes are as follows: a. SR-IOV/PCI Pass-through: Current system configuration does not support
network SR-IOV or network PCI Pass-through. b. SR-IOV: System was tested using SR-IOV where a virtual network
adapter was given to the SLES 12 FV guest. One of the embedded <add network adapter used> adapters was used in
this testing.
Requirements
• 4 CPU cores, minimum
• 4 GB of RAM minimum, plus 256 MB of RAM for each addition CPU (if > 4 cores) on the base system.
• 250 GB hard disk space minimum. See Windows Server webpage for minimum hard disk requirements.
• A Virtual Machine with maximum configuration (VMM guest) must be tested prior to the multiple VM guest
testing.
• 3 virtual machines (Choose from SLES 11 SP4, SLES 12 SP3, Windows 2008, Windows 2012 ). See table
on next page.
• The paravirtualized drivers are required for Windows certifications. A business case must be presented to
waive this requirement.
• The SLES 12 SP3 the “Virtualization with Xen” documentation is available from:
https://www.suse.com/documentation/
• The SLES 11 SP4 the “Virtualization with Xen” documentation is available from:
https://www.suse.com/documentation/sles11/book_xen/data/book_xen.html
• The Virtual Machine Driver Pack For SLES 11 SP4, SLES 12 and later is available from:
https://download.suse.com/Download?buildid=oFkYuBj6MDI~
89 Xen Virtual Machine Tests

Xen Operating Systems for Certification
Table 4-6 SLES 11 SP4 VT Hardware

VT Hardware Host Paravirtualized 64- VMM Guest
bit Paravirtualized 64-bit
Recommendation SLES 11 SP4 SLES 12 SP3
Alternatives SLES 11 SP4

VT Hardware Host Paravirtualized VM1 Guest VM2 Guest VM3 Guest
64-bit Paravirtualized Fully-virtualized Fully-virtualized
Recommendation SLES 11 SP4 SLES 12 SP3 SLES 12 SP3 Windows 2008 SP2 (32
bit)
Windows 2008 SP2 (64
Alternatives SLES 11 SP4 SLES 11 SP4 (64 bit) bit)
Windows 2008 R2 (64
bit)
Windows 2012 (64 bit)
For Network PCI Pass- SLES 11 SP4
Through the VM must
be a fully virtualized
SLES Guest.

VT Hardware Host Paravirtualized 64- VMM Guest
bit Paravirtualized 64-bit
Recommendation SLES 12 SP3 SLES 12 SP3
Alternatives SLES 11 SP4

VT Hardware Host Paravirtualized 64- VM1 Guest VM2 Guest VM3 Guest
bit Paravirtualized Fully-virtualized Fully-virtualized
Recommendation SLES 12 SP3 SLES 12 SP3 SLES 12 SP3 Windows 2008 SP2 (32
bit)
Windows 2008 SP2 (64
Alternatives SLES 11 SP4 SLES 11 SP4 (64 bit) bit)
Windows 2008 R2 (64
bit)
Windows 2012 (64 bit)
For Network PCI Pass- SLES 11 SP4
Through the VM must
be a fully virtualized
SLES 11 SP4 Guest or
a SLES 12 SP3 Guest.

(en) 6 April 2007
Figure 4-1 Xen Testing Configuration(SLES)
4.1a Installing a Xen Virtual Machine

The following instructions enable you to install a virtual machine on the SUT.
_____________________________________________________________________________________________
Note: The first Xen Guest installation must be a fully virtualized (FV) SLES guest and must be installed via DVD
media. This is necessary so that the optical test will be set up correctly.
_____________________________________________________________________________________________
Configure the Xen Host server (domain 0)

1 Log in as root.
2 Enter the password (suse).
3 Open a terminal.
4 For SLES 11 type yast2 xen <Enter>. For SLES 12 SP3 select 'XEN Sever & XEN Tools' then click on Accept.
5 For SLES 11, Click the box next to Xen, then click accept. If prompted to install packages, click continue or
install to install the packages.
6 If prompted by the Xen Network Bridge question (configure a default bridge) click Yes. For a UEFI enabled system
set the bootloader to Xen as the default by following the steps below.
6a Open a terminal.
6b Type Yast2 bootloader <Enter>.
6c For SLES 11 SP4 click on Xen, then click on the “Set as default” button. For SLES 12 SP3 click the
BootLoader options Tab. Select the OS version with XEN Hyperviser.
6d Click OK.
7 If prompted read the message, click OK then reboot and select the Xen section in the boot loader menu.
8 Log in as root , enter the password (suse).

9 Open a terminal.
10 Type vm-install <Enter>. This install is supported on SLE 11 and SLES 12 SP3. There is a new installation
method which can be used with SLES 12 SP3. See section 4.1b Installing a Xen Virtual Machine for the new
SLES 12 SP3 installation method.
11 Click Forward.
12 If needed, select I Need To Install An Operating System.
13 Click Forward.
14 Click the type of operating system you are installing.
15 Click Forward.
16 Verify that the correct Virtualization method is selected. If needed, click Virtualization method to change the
virtualization type (Full virtualization or Paravirtualization).
17 Name the virtual machine.
17a Click Name of Virtual Machine.
17b Enter a unique name for the virtual machine
17c Click Apply.
18 Configure the Hardware.
18a Click Hardware.
18b For the VMM guest configure up to the maximum RAM of what the hardware product supports. For the 3
virtual machine guests configuration change the maximum memory and initial memory to ¼ of the total
memory in SUT. Minimum of 1024 MB. Maximum of 16 GB memory for the 32 bit SLES guest when
running on a 64-bit Host OS. The 64 bit SLES guest can have up to 512 GB of RAM.
18c For the VMM guest configure as many CPU's as available. For SLES 11 hosts configure ¼ of the logical
processors on each VM. For SLES 12 hosts configure the 3 virtual machine guests using the following table
to determine the number of processors to assign to each of the 3 virtual machines.
This table does not apply to the VMM guest.
________________________________________________________________________________________
Guest Operating System on SLES 12 Set Virtual Processors setting to:
________________________________________________________________________________________
SLES 11 SP4 1/3 of 2x of the total logical processors in SUT. Minimum of 1 processor up to a maximum of 64
processors. Note: Each guest should not have more vcpus than there are lcpus.
SLES 12 SP3 1/3 of 2x of the total logical processors in SUT. Minimum of 1 processor up to a maximum
available host processors. Note: Each guest should not have more vcpus than there are lcpus.
Windows Server 1/3 of 2x of the total logical processors in SUT. Minimum of 1 processor up to a maximum of
what is allowed by the Windows license. Note: Each guest should not have more vcpus than there
are lcpus.
______________________________________________________________________________________________________
18d Click Apply.

19 Click Disks.
20 Click Edit (first ensure that the hard disk is highlighted).
21 Change the size to be at least 16 GB for the 2nd VM Guest, then at least 8.0 GB in the Size field for the others –

VMM Guest, 1st and 3rd VM Guest.
22 Ensure that the “Create sparse file image file” is not checked.
23 Click OK.
24 Click Apply.
There are multiple methods to install the Xen Guest (virtual machines). We recommend using a network
installation method or PXE for the SLES guests. Three methods are listed below along with instructions. Use the
one which best meets your needs. Skip the next section entitled 4.1b Installing a Xen Virtual Machine (steps 1
through 7).
4.1b Installing a Xen Virtual Machine

For SLES 12 SP3 there is a new VM wizard. The New VM wizard helps you through the steps required to create a
virtual machine and install its operating system. There are two ways to start it: Within Virtual Machine Manager either
click the Create New Virtual Machine icon or choose File › New Virtual Machine. Alternatively, start YaST and
choose Virtualization › Create Virtual Machines for Xen and KVM.
1 Start the New VM wizard either from YaST or Virtual Machine Manager.
2 Choose an installation source - either a locally available media or a network installation source. If you would like to
set up your VM Guest from an existing image, choose import existing disk image.
On a VM Host Server running the Xen hypervisor, you can choose whether to install a paravirtualized or a fully
virtualized guest. The respective option is available under Architecture Options. Depending on this choice, not all
installation options may be available.
3 Depending on your choice in the previous step, you need to provide the following data:
Local Installation Media:

Specify the path on the VM Host Server to an iso image containing the installation data. If it is available as a
volume in a libvirt storage pool, you can also select it via the Browse button (see Chapter 12, Managing Storage
for more information). Alternatively, choose a physical CDROM or DVD inserted in the optical drive of the VM
Host Server.
Network Installation:
Provide the URL pointing to the installation source. Valid URL prefixes are, for example, ftp://, http://, https://,
and nfs://. Under URL Options you may provide a path to an auto-installation file (AutoYaST or Kickstart, for
example) and Kernel parameters. Having provided a URL, the operating system should be automatically be
detected correctly. If this is not the case, deselect Automatically Detect Operating System Based on Install-Media
and manually select the OS Type and Version.
Network Boot (PXE):

When booting via PXE, you only need to provide the OS Type and the Version.
Import an Existing Image:

To set up the VM Guest from an existing image, you need to specify the path on the VM Host Server to the image.
If it is available as a volume in a libvirt storage pool, you can also select it via the Browse button (see Chapter 12,
Managing Storage for more information).

4 Choose the memory size and number of CPUs for the new virtual machine.
4a For the VMM guest configure up to the maximum RAM of what the hardware product supports. For the 3
virtual machine guests configuration change the maximum memory and initial memory to ¼ of the total memory
in SUT. Minimum of 1024 MB. Maximum of 16 GB memory for the 32 bit SLES guest when running on a 64-
bit Host OS. The 64 bit SLES guest can have up to 512 GB of RAM.
4b For the VMM guest configure as many CPU's as available. For SLES 11 hosts configure ¼ of the logical
to determine the number of processors to assign to each of the 3 virtual machines.
This table does not apply to the VMM guest.
_______________________________________________________________________________________
_______________________________________________________________________________________
SLES 11 SP4 1/3 of 2x of the total logical processors in SUT. Minimum of 1 processor up to a maximum of 64
processors. Note: Each guest should not have more vcpus than there are lcpus.
SLES 12 SP3 1/3 of 2x of the total logical processors in SUT. Minimum of 1 processor up to a maximum
available host processors. Note: Each guest should not have more vcpus than there are lcpus.
Windows Server 1/3 of 2x of the total logical processors in SUT. Minimum of 1 processor up to a maximum of
what is allowed by the Windows license. Note: Each guest should not have more vcpus than
there are lcpus.
_______________________________________________________________________________________
5 This step is omitted if having chosen Import an Existing Image in the first step.
Set up a virtual hard disk for the VM Guest. Either create a new disk image or choose an existing one from a storage
pool. If you choose to create a disk, a qcow2 image will be created under /var/lib/libvirt/images. The disk size
should be least 16 GB for the first VM Guest, then at least 8.0 GB in the Size field for the 2nd and 3rd VM Guest.
6 The last screen of the wizard lets you specify the name for the virtual machine. Options to specify the network
device and the MAC address can be found under Advanced Options. If you need to customize the configuration in
detail before the installation, activate the relevant check box. Exit the wizard with Finish. Depending on your
choice, this will either start the installation or open the VM Guest configuration screen.
7 The OS installation will begin. If the Test Kit installation occurs after the OS install, then follow the steps in
Section 4.4, “Configuring Xen for the PCI Pass-Through”. Otherwise follow the steps in ”Section 2.4, “Installing
the Test Kit on the SUT”.

For a ParaVirtualized SLES OS Network installation do the following (Recommended):
1 Click Operating System Installation.
2 Select PXE Boot.
3 Choose a SLES OS to install from the dropdown field. For the PXE installation, only choose from the SLES OS
listings which contain the word Xen in the filename. Skip to step 8.
Or the following install method can be used.

2 Click the Network URL radio button.
3 Enter the name of the OS install directory located on TC in /home/InstSource/ as follows:
nfs://[TC IP address]/home/InstSource/[DVD ISO installation directory on TC]
Please note that the default information in this field may not be the correct information. The field may also appear
blank and will need to be filled in. Ensure that the path and filename information are accurate. This OS name
should be the same OS and architecture as selected in step 14 above.
4 Click the find button next to the AutoYaST file text box to browse on SUT.
5 For SLES 11 browse to the /opt/suse/testKits/system/autoyast/ directory. For SLES 12 SP3 browse to
nfs://[TC IP address]/opt/suse/testKits/system/autoyast/ directory.
6 Select the xml file for the OS to install. This xml file should be the same OS and architecture as selected in step 3.
SLES 11 Example: SLES_11_SP4-x86_64-vm.xml
7 Click Open.
8 Click Apply.
9 Click OK. The OS installation will begin. The install process will remain at the install screen.
10 The paravirtualized Xen guest GUI may not start. If this happens, it can be corrected by using sax2. To set up the
GUI do the following:
10a Login as root, password suse (in the terminal interface).
10b In the prompt type sax2 -r <Enter>.
10c Click OK.
10d Type init 3 <Enter>.
10e There will not be a prompt, just a blank space with after the message “Master Resource control: run level 3.... “
Press <Enter> to gain a prompt.
10f Type init 5 <Enter>. Then the GUI will start.
11 When the Installation completes then follow the steps in section ”Section 2.4, “Installing the Test Kit on the SUT”.

For a Fully Virtualized SLES OS Network installation do the following (Recommended):
2 Click the PXE Boot radio button.
3 Click Apply.
4 Click OK.
5 The Xen Guest Console window (Virt Viewer) will display a PXE menu which includes the option "SUSE SCK
Menu" .
6 Select the "SUSE SCK Menu" option and press "Enter".

7 The SUSE SCK Menu will display the different operating systems that the user may choose to install. If the SUSE
SCK Menu does not display the desired operating system, repeat the steps in
Section 2.2.3, “Setting up the DHCP/PXE server on TC” then Section 2.2.4, “Adding ISO images to the PXE menu
on TC”. Choose an OS install with a single disk description then press <Enter>. This OS name should be the
same OS and architecture as selected in step 14 above.
Example: SLES11_SP4 x86_64 single disk automated install
8 The OS installation will begin. If the Test Kit installation occurs after the OS install, then follow the steps in
Section 4.4, “Configuring Xen for the PCI Pass-Through”. Otherwise follow the steps in ”Section 2.4, “Installing
the Test Kit on the SUT”.
For Paravirtualized or Fully Virtualized DVD media or ISO (including Windows) installations do the
following:
1 Insert the OS installation DVD into the system or copy the ISO image onto the hard drive on SUT.
3 Select Virtual Disk.
4 Click Add.
5 Type in the path to the DVD-ROM Drive (example /dev/dvd) or point to the ISO image on SUT.
6 Click OK.
7 Click Apply.
8 If installing a Windows guest complete the following:
8a Click Network Adapters.
8b Ensure that the LAN Adapter is highlighted then click edit.
8c Change the source to the second bridge (br2 or the 10.1.2.1 network)
8d Click Apply.
8e Click Apply again.
8f Select the Windows OS installation location in the operating system installation section.
8g Click open, then click OK.
8h Click Apply.

9 Click OK.
10 Please refer to the appropriate section for the VM installation:
• Section 4.7, “Installing a 2008, or 2012 Virtual Machine”
• Section 6.1, “Manually Installing SLES on SUT” begin at Step 2.
4.1c Automated Installation of a Xen Virtual Machine

We provide a script that automates installing SLES 11 VM's and 12 VM's on SLES 11 hosts and 12 hosts running the
XEN or KVM hypervisor. The script leverages the existing PXE/DHCP server and autoyast files on TC. The script
detects the host's SLES version and hypervisor and calls vm-install or virt-install as appropriate. The script can be
started with or without passing paramters. The script is located on SUT at /opt/suse/testKits/system/bin/
Starting the script without passing parameters.

When starting the script without passing parameters it will present a menu of SLES releases to choose for the VM.
Then the VM name, amount of RAM, disk location, and number of vCPUs can be specified. Next, the script takes
care of the rest of the installation details. To see which ISO's are available on TC run the script without any options.
On SUT use the command:
/opt/suse/testKits/system/bin/install_vm
Starting the script with passing parameters.

The VM install can be completely unattended by passing parameters to "install_vm" script indicating the number of
VMs to install and the location for VM(s) disk storage. The script calculates CPU and Memory available on the host
and assigns 80% of memory and all vcpus to one Max VM (when installing one VM) or divides memory and vcpus
equally among VMs when installing multiple VMs. Before starting installation, the script presents a summary of VM
to be installed and allows the user to change any or all settings for each VM if necessary. The script determines the
VM OS release to be installed based on existing ISO's, and autoyast files on TC. vCPUs in multiple VM installs will
be overcommited by a factor of 2x, this number can vary depending on whether hyperthreading is enabled.
Please change to the /opt/suse/testKits/system/bin/ before trying the examples.

This example will install one Max VMM and create a storage pool in directory /home:
./install_vm -c 1 -p /home
This example will install 3 VMs, create a storage pool in /data dir, and leave enough resources for one future VM:
./install_vm -c 3 -p /data -w 1
For script help, details, requirements and known issues please use -h option:
/opt/suse/testKits/system/bin/install_vm -h
4.2 Using SLES Virtual Machines – Help Section
For a Fully virtualized installation of SLES 11 SP4 please note the following:
1 Maximize the install window and use the scroll bars as needed to access the other areas on the screen.
2 In each window created from the virt manager <Ctrl-Alt> can be used gain mouse pointer screen access.
3 If the VM was installed via a local ISO image or local DVD then remove the Virtual DVD by doing the following:
3a In a console window open the Virtual Machine Manager by typing virt-manager <Enter>.

3b Highlight the desired virtual machine. Click "Open" to open the virtual machine console.
3c In the virtual machine console, click "Shutdown" to stop the virtual machine. (The virtual machine must
be stopped in order to remove the virtual DVD).
3d In the virtual machine console, click View → Details.
3e On the left side of the window, click on the Virtual DVD. (Make sure the icon shows a CD/DVD).
3f Click "Remove".
3g Close and exit the Virtual Machine Manager and the guest console.
4 The virtualization guide documentation is available on line.
The virtualization guide documentation for SLES 11 SP4 is available at:
https://www.suse.com/documentation/sles11/book_xen/data/book_xen.html

5 Begin testing by starting at Section 2.5, “Updating the Products.txt File”.
4.3 Manually Installing the Test Kit on the SLES Xen Virtual Machine
1 On the SUT, log in as root.
2 Start all VM's.
3 On the TC, log in as root.
4 Open a terminal on TC, then type sck_copy_install_files.sh <Enter>. The file is located in /home/InstSource/sck/.
5 Enter the IP address of the Guest VM to install the Test Kit onto then press <Enter>.
6 Follow the on screen instructions on the TC. The on screen instructions will include which guest VM to run
sck_install.
7 A terminal window will display the System Test Kit install prompt.
8 Choose “Xen Guest” install by pressing 2 <Enter>.
10 The NIC Configuration Menu will appear. The proposed IP address numbers will be listed. The purpose of this
menu is to confirm or change the assigned IP address information. Change the IP address information as needed
by typing the NIC number (example 1) then <Enter>. Press C <Enter> if the displayed information is correct and
all changes have been made.
11 Press <Enter> as prompted once the Test Kit installation has completed and exit the terminal window.
12 Right-click on the time display in the Display panel.
13 Click Preferences.
14 Select 12 hour in the box next to Clock Type.
15 Select Show Seconds.
16 Click Close.
17 Repeat steps 4-16 for each associated VM (SLES 11 SP4 VM).

18 Verify this system has the same time setting as TestConsole (see Section A.4, “Time Synchronization” for more
information).
19 If the PCI Network Pass-Through functionality has not yet been set up on the SLES fully virtualized VM, then
proceed to Section 4.4, “Configuring Xen for the Network PCI Pass-Through”. To install another virtual
machine return to Section 4.1, “Installing a Xen Virtual Machine”. Otherwise begin testing in Section 2.5,
“Updating the Products.txt File”. The testing section is intended to be followed section by section until the testing
is completed.
4.4 Configuring Xen for Network PCI Pass-Through

We require Network PCI Pass-Through or SR-IOV to be tested on all SLES versions released after SLES 11 SP4
during Yes Certification. This is a choice to use either Network PCI Pass-Through or SR-IOV on one of the fully
virtualized SLES XEN guests versions released after SLES 11 SP4. We recommend that one of the embedded
network adapters be used as the pass-through adapter, but an additional adapter can be used and noted on the
submission. If network pci pass-through is not supported on the NIC skip to step 20 in this section. The Test Kit
defaults to use VM2 for the PCI Pass-Through.
1 If the host system is Intel processor-based then host must be booted with the following boot parameter:
intel_iommu=on. To add intel_iommu=on to the boot loader Click Applications menu → System Tools →
Yast → Boot Loader → Kernel Tab, then edit the kernel line.
____________________________________________________________________________________________
Note: If the host system is AMD processor-based you will not need the intel_iommu boot parameter but you will
need to make sure the IOMMU extension is set to “on” or “enabled” in the system setup utility before proceeding.
Boot the system.
____________________________________________________________________________________________
___________________________________________________________________________________________
Note: In addition to steps below we provide a script that automates the steps for assigning a NIC via PCI
Pass-through or SR-IOV (VF NIC) to a VM. You may run the script on SUT with command:
/opt/suse/testKits/system/bin/sriov_setup
For script requirements and known issues run on SUT: /opt/suse/testKits/system/bin/sriov_setup -h

Now skip to step 15.
____________________________________________________________________________________________
2 Select a device to reassign to a fully virtualized VM Guest. To do this run “lspci | grep Ethernet” on a terminal in
the host and determine the device number. For example, if lspci contains the following line:
16:00.0 Ethernet Controller: Intel Corporation 82572EI Gigabit Ethernet Controller

then the PCI number is (16:00.0).
___________________________________________________________________________________________
Note: During standard certification two network adapters or ports are required. The adapter being passed through
to the virtualized guest should be one of the embedded adapters in the system or also be an “additional” adapter or
chipset beyond the original two adapters in the system. This additional network adapter should not be configured
in the host system, it will be passed through to the guest then configured in the guest.
___________________________________________________________________________________________

3 Start the Virtual Machine Manager on the system host: Yast → Virtualization → Virtual Machine Manager
4 Close Yast.
5 If the SLES guest you will be passing the network adapter to is running it should be shutdown.
6 Once the guest is grayed-out (shutdown) in the Virtual Machine Manager you can proceed with the configuration.
7 Right click on the greyed-out guest in the Virtual Machine Manager and select Open. (Do not start the guest OS)
8 Select View then select Details.
9 Remove the existing virtual network adapter (e.g., NIC :59:3c:f5), right click on the adapter then select “– Remove
Hardware” or highlight and click “-Remove”. Select “Yes” when prompted “Are you sure you want to remove this
device?”.
10 Click the “+ Add Hardware” button in the lower left corner.

11 Select “PCI Host Device” from the left side menu options.
12 Scroll through the “Host Device” list until you find the adapter that will be passed through; for example “16:00.0
82572EI Gigabit Ethernet Controller”
13 Select the adapter in the list then click Finish.

_________________________________________________________________________________________
Note: The pass-through LAN adapter hardware should be physically cabled to the second network test hub
(e.g., 10.1.2.x network) and the IP address will be 10.1.2.x.
_________________________________________________________________________________________
14 From the menu options at the top guest select View and change Details back to Console.
15 Boot the guest and login.
16 From a terminal in the guest run “lspci” to validate the pass-through adapter is present. Run “yast2 lan” from the
terminal command prompt. The passed through network adapter should be available in the guests Network
Settings, Overview tab.
_________________________________________________________________________________________
Note: If the virtual network adapter is still listed in Yast – Network Settings, click on it then click Delete to
remove it.
_________________________________________________________________________________________
17 Now select the network adapter that has been passed through to the guest, click edit and configure it with the IP
address 10.1.2.12 and Subnet Mask 255.255.255.0. Change the VM3 10.1.3.1 IP address in the test project to
become 10.1.2.12.
18 Click Next then OK to save the pass-through adapters network configuration. The pass-through network adapter
should now be assigned directly to and functioning in just that guest; you may want to validate with the network
connection with a ping from the pass-through guest to another system.
___________________________________________________________________________________________
Note: ntp time synchronization may need to be restarted on the guest: “/etc/init.d/ntp restart” will reset ntp if
needed.
___________________________________________________________________________________________

19 If the Test Kit was installed on the VM prior to PCI Pass-Through NIC assignment, then run
/opt/suse/testKits/system/bin/post_subnet_change.sh on the VM and answer the questions.
20 To install another virtual machine return to Section 4.1, “Installing a Xen Virtual Machine”.
Otherwise begin testing in Section 2.5, “Updating the Products.txt File”. The testing section is intended to be
followed section by section until the testing is completed.
4.5 Configuring XEN for SR-IOV

We require Network PCI Pass-Through or SR-IOV to be tested on SLES versions released after SLES 11 SP4 during
Yes Certification. This is a choice to use either Network PCI Pass-Through or SR-IOV on one of the fully virtualized
SLES XEN guests versions released after SLES 11 SP4. This section provides the steps to configure SR-IOV on a
XEN guest. We recommend that one of the embedded network adapters be configured SR-IOV, but an additional
adapter can be added and used for SR-IOV then noted on the submission. If SR-IOV is chosen, then one of the
embedded network adapters should be used as the SR-IOV adapter, but an additional SR-IOV adapter can be added
and used then noted on the submission.
Requirements
• SR-IOV-capable network card (as of SUSE Linux Enterprise Server 12 only network cards support SR-IOV)
• x86_64 host supporting hardware virtualization (AMD-V or Intel VT-d)
________________________________________________________________________________________

________________________________________________________________________________________
1 In the system BIOS, enable the virtualization (example Intel vt-d).

2 Enable iommu in the hypervisor (e.g. add boot parameter intel_iommu=on on the linux commandline of the host) at
boot. If the host system is AMD processor-based you will not need the intel_iommu boot parameter but you will
3 Verify that the NIC driver supports sr-iov by opening a terminal then typing "lspci -v". A device that supports SR-
IOV reports a capability similar to the following:
Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV).
4 Check whether the SR-IOV driver is already loaded by running lsmod. In the following example a check for the
be2net driver (Emulex OneConnect 10Gb NIC) returns a result.
lsmod | egrep "^be2net "

If the driver is loaded, unload it
modprobe -r be2net
5 Load the SR-IOV driver with the VFs parameter. For example for be2net driver:
modprobe be2net num_vfs=2
To find out the correct VFs parameter for your driver, issue command "modinfo <drivername>" and look at "parm:"
sections.
6 Run "lspci | grep Ethernet" command and verify additional Virtual NICs were created.
7 Make loading NIC driver with VFs parameter persistent by adding the VFs driver option to /etc/modprobe.d/99-
local.conf file. For example, for be2net driver:
echo "options be2net num_vfs=2" >> /etc/modprobe.d/99-local.conf
and run command "mkinitrd" to refresh the driver configuration there
8 Reboot the machine and check if the SR-IOV driver is loaded.

9 Once the SR-IOV hardware is properly set up on the VM Host Server, you can add VFs to VM Guests. In order to
do so, you need to collect some data first. The following procedure is using example data. Make sure to replace it
by appropriate data from your setup.
_____________________________________________________________________________________________
Note: The following procedure is using example data. Make sure to replace it by appropriate data from your setup.
_____________________________________________________________________________________________
10 Use the virsh nodedev-list command to get the PCI address of the VF you you want to assign and it's
corresponding PF. Numerical values from the lspci output shown in Section 10.7.2, Load and configure the SR-
IOV Host drivers (for example 01:00.0 or 04:00.1) are transformed by adding the prefix "pci_0000_" and by
replacing colons and dots with underscores. So a PCI ID listed as "04:00.0" by lspci is listed as
"pci_0000_04_00_0" by virsh. The following example lists the PCI IDs for the second port of the Intel 82576NS
network card:
~ > virsh nodedev-list | grep 0000_04_

pci_0000_04_00_0
pci_0000_04_00_1
pci_0000_04_10_0
pci_0000_04_10_1
pci_0000_04_10_2
pci_0000_04_10_3
pci_0000_04_10_4
pci_0000_04_10_5
pci_0000_04_10_6
pci_0000_04_10_7
pci_0000_04_11_0
pci_0000_04_11_1
pci_0000_04_11_2
pci_0000_04_11_3
pci_0000_04_11_4
pci_0000_04_11_5

The first two entries represent the PFs whereas the other entries represent the VFs.
11 Get more data that will be needed by running the command virsh nodedev-dumpxml on the PCI ID of the VF you
want to add:
~ > virsh nodedev-dumpxml pci_0000_04_10_0

<device>
<name>pci_0000_04_10_0</name>
<parent>pci_0000_00_02_0</parent>
<capability type='pci'>
<domain>0</domain>
<bus>4</bus>
<slot>16</slot>
<function>0</function>
<product id='0x10ca'>82576 Virtual Function</product>
<vendor id='0x8086'>Intel Corporation</vendor>
<capability type='phys_function'>
<address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</capability>
</capability>
</device>
The following data is needed for the next step:
<domain>0</domain>
<bus>4</bus>
<slot>16</slot>
12 Create a temporary XML file (for example /tmp/vf-interface.xml containing the data necessary to add a VF
network device to an existing VM Guest. The minimal content of the file needs to look like the following:
<interface type='hostdev' managed = 'yes'> (See A below)

<source>
<address type='pci' domain='0' bus='11' slot='16' function='0'/> (See B below)
</source>
</interface>
12a VFs do not get a fixed MAC address, it changes everytime the host reboots. When adding network
devices the "traditional" way with <hostdev>, it would require to reconfigure the VM Guest's network
device after each reboot of the host, because of the MAC address change. To avoid this kind of problems,
libvirt introduced the "interface type='hostdev'" directive, which sets up network specific data before
assigning the device.
12b Specify the data you acquired in the previous step here.
13 Last, add the VF interface to an existing VM Guest. With the guest running, you may list and find their IDs with
command "virsh list"
linux-s46s:~ # virsh list

Id Name State
----------------------------------------------------

2 sles11 running
3 sles12-x86_64 running
virsh attach-device GUEST /tmp/vf-interface.xml --config
virsh attach-device sles12-x86_64 /tmp/vf-interface.xml --config
where GUEST is the name or ID of the guest –config
This option will only affect the persistent XML, even if the domain is running., The device will only show up
in theguest on next boot
14 Shutdown guest VM and re-start for new configuration with SR-IOV card to take effect.
15 Go to yast2 lan on the guest and select the network adapter that has been passed through to the guest, click edit
and configure it with the IP address 10.1.2.x and Subnet Mask 255.255.255.0.
_______________________________________________________________________________________
remove it.
_______________________________________________________________________________________
16 If the Test Kit was installed on the VM prior to SR-IOV NIC assignment, then run
17 To install another XEN virtual machine return to Section 4.1, “Installing a Xen Virtual Machine”. , Otherwise
begin testing in Section 2.5, “Updating the Products.txt File”.
___________________________________________________________________________________________
Note: Some network cards such as Intel 82576NS may require a special SR-IOV driver to be loaded. Follow the
instructions of your specific card to load the correct SR-IOV driver.
___________________________________________________________________________________________
4.6 Installing a Windows 2008 or 2012 Virtual Machine

1 Follow the prompts to install Windows with the default typical settings.
2 We suggest using the following IP addresses. The default IP address in the test project for this Windows guest may
need to be changed. Three VM's are required for Xen certification.
________________________________________________________________________________________
____________________________________________________________________________________________
SLES VM Guest 1 10.1.1.11
SLES VM Guest 2 10.1.2.12 (If supported by the NIC, this VM is used for
PCI Pass-Through /SRIOV)
Windows VM Guest 5 10.1.1.15
____________________________________________________________________________________________
_______________________________________________________________________________________

Note: To send keystrokes to the Windows 2008 VM use the send key drop down located at the top of the VM
window to select the keystrokes.
_______________________________________________________________________________________
3 Be sure to disable all firewalls (domain, private, public).

4 Install the virtual machine driver pack for Windows onto the Xen Windows guest. The virtual machine driver pack
is available from:
For SLES 11 SP4, SLES 12 and later:

5 The virtualization documentation for SLES is available online:

The virtualization guide documentation for SLES 11(latest support pack) is available from:
https://www.suse.com/documentation/sles11/
6 Continue to Section 4.7, “Installing the Test Kt on the Windows Virtual Machine”.
4.7 Installing the Test Kit on the Windows Virtual Machine

1 Verify Samba is running on TC (must be performed if TC is rebooted)
1a On the TC terminal type /etc/init.d/smb status <Enter>.
1b If the status is “running” then Samba is running. Otherwise start Samba by typing: /etc/init.d/smb start
<Enter> at the command prompt or reboot TC.
2 Set the static IP address on the Windows VM.
2a On 2008 click on Start -> Control Panel -> Network Connections -> Local Area Connection.
2b On Windows Server 2008 right click on local area network connection, network and sharing center then
click “Manage Network Connection” link.
2c On Windows 2012:
2c1 Press the windows key. If the windows key is not working then click on the the Virtual hardware details
button (it looks like a blue circle with an “i”) at the top. Select display, then select VNC. Select the key map
to be en-us. Click Apply.
2c2 Click on Control Panel.
2c3 Click on View Network Status + Tasks.
2c4 Click on Ethernet (next to connections).
2d Click on Properties.
2e For Windows Server 2008 and 2012 click on Internet Protocol version 4 (TCP/IPv4) -> Properties .
2f Click on Use the following IP address.
2g Enter the IP address (e.g. 10.1.1.15) . The windows IP address will also need to be changed in the test project on
TC.

2h Enter the Subnet mask (e.g. 255.255.255.0).
2i Enter the default gateway of the xen host (e.g. 10.1.1.1).
2j Click on OK -> Close.
2k Click on Close.
3 Map drive T: to \\<IP address of TC>\windir\

3a Click on Start -> Computer on Win2008.
3b On Win 2012 press windows button+e, then click computer, then choose Map Network Drive → Map Network
Drive (again).
3c On 2008 click on Tools -> Map Network Drive.
3d Select Drive T:
3e Type \\<IP address of TC>\windir\ (e.g. \\10.1.1.2\windir\)
3f Click finish.
3g Enter the TC username (root) and password (suse).
4 On Windows 2008 (all versions), share the file access with the Linux OS.
4a Right click on "Start", select "Explore".
4b Right Click on "Local Disk(C:)", Select "Share..."
4c Click the "Advanced Sharing..." button.
4d Check the "Share this folder" box, then click the "OK" button.
4e Click the "Network and sharing center" link.
4f Click the "Public Folder Sharing" pull down menu arrow.
4g Click the "Turn on sharing so anyone with network access can open files" radio button,
4h Click the apply button.
5a Press the window button + e to open Windows Explorer.
5b Right click on "Local Disk(C:)", select "Share with".
5c Click on "Advanced Sharing".
5d Click on the “Advanced Sharing” button.
5e Check the "Share this folder" box, then click the "OK" button.
5f Click the "Network and Sharing Center" link.
5g Click on the All Networks Arrow to expand the section.
5h Click the "Turn on sharing so anyone with network access can open files" radio button.
5i Click the “Turn off password protection sharing...” radio button.
5j Click Save Changes.
5k Click Close.

6 Run Tclink on the Windows VM.
6a Double click the following file: T:\suseTestKits\system\bin\XpClient.bat. In Windows 2012, this file will
be locatable in the Windows Explorer window used in step 3 above.
6b Click Run.
7 To install another Xen virtual machine return to Section 4.1, “Installing a Xen Virtual Machine” step 9, Otherwise
begin testing in Section 2.5, “Updating the Products.txt File”.
4.8 Preparation For Quick Install Of Virtual Machines

Once you have installed virtual machines as described in Section 4.1, “Installing a Virtual Machine” and the virtual
machine passes certification tests. Follow this procedure to save the virtual machine images so they can be reused
with a simple procedure (file copy of the image and quick install) This should save you hours when setting up a SUT
for testing Xen.
1 Locate or build a stable machine (that you don't intend to re-install the OS) with enough free disk space to hold at
least 3 Virtual Machine Images (typically 8GB each).
2 On the stable machine, change directory to where you want to store the images.
Example: cd /xen-images/
3 Create a unique directory to copy the image file to.
Example: md ./sles10-sp42-i386-pv/
4 Copy the image file from the SUT to the newly created directory on the stable machine.
Example 1: scp -rp <IP_Address_Of_SUT>:/var/lib/xen/images/sles10/* ./sles10-SP4-i386-pv/
Example 2: scp -rp 10.1.1.1:/var/lib/xen/images/sles10/disk0 ./sles10-SP4-i386-pv/
4a If prompted about the RSA key fingerprint... continue connecting? Enter yes.
4b Enter the root password of the machine being copied from.
4.9 Quick Install Of Virtual Machines

1 Copy an image file that was saved in Section 4.8 “Preparation For Quick Install Of Virtual Machines” that you want
to install:
1a On the SUT, change directory to /var/lib/xen/images/
1b Create a unique directory to copy the image file to.
Example: md ./sles10-SP4-i386-fv-1/
1c Copy the image file from the stable machine to the SUT using the scp utility.
Example 1: scp -rp <IP_Address_Of_Stable_Machine>:/<Path_To_Images>/<image_dir>/* ./<new_image_dir>
Example 2: scp -rp 10.1.1.1:/xen-images/sles10-SP4-i386-fv/disk0 ./sles10-SP4-i386-fv-1/
1c If prompted about the RSA key fingerprint... continue connecting? Enter yes.
1d Enter the root password of the machine being copied from.

2 Do steps 6-10 of Section 4.1 “Installing a Virtual Machine”.
3 Select I have a disk or disk image with an installed operating system.
4 Click Forward.
5 Click the type of operating system you are installing (based on the descriptive name of the directory that contains
the disk image that you copied in step 1).
6 Click Forward.
7 Do steps 15-18 of Section 4.1 “Installing a Xen Virtual Machine”.
8 Click Hard disk.
9 Click Browse and browse to the image file that was copied in step 1.
10 Do steps 21-22 of Section 4.1 “Installing a Xen Virtual Machine”.
11 At this point the virtual machine should boot up.
12 Make sure the IP address is unique, if it is not, change it:
12a For SLE see Section 2.3.1, “Installing SLE on the SUT through PXE”.
13 Make sure the certification Test Kit is up to date, if not, reinstall it:
13a For SLES see Section 2.4 “Installing the Test Kit on the SUT”.
14 At this point, the virtual machine should be ready use for testing.

5
Kernel-based Virtual Machine Tests
Before the Kernel-based Virtual Machine (KVM) can be configured on the SUT, please follow the instructions in
Section 2.3.1, “Installing SLE on SUT through PXE” including “Installing the Test Kit on the SUT”. The goal of this
test is to certify a Virtual Machine with maximum configuration (VMM guest) of available RAM and available CPU's
then to certify 3 KVM's on the 64 bit OS host simultaneously. The 3 KVM's can all be the same SLES OS. After the
VMM guest is tested it must be either re-configured to become the VM1 guest or it should be shut down or deleted. If
you are certifying more than 3 KVM's contact SUSE prior to certification testing. We require that the hardware be
certified with SLES 12 SP3 or SLES 11 SP4 only (bare metal/base cert), prior to the SLES 12 SP3 or SLES 11 SP4
KVM certifications.
We require Network PCI Pass-Through or SR-IOV to be tested on all SLES versions after SLES 11 SP4 during Yes
Certification (if a LAN adapter in the SUT supports the functionality). A configuration Note must be added to all
KVM bulletins (for SLES versions after SLES 11 SP4) for Network PCI Pass-Through or SR-IOV. Examples of the
configuration notes are as follows: a. SR-IOV/PCI Pass-through: Current system configuration does not support
network SR-IOV or network PCI Pass-through. b. SR-IOV: System was tested using SR-IOV where a virtual network
adapter was given to the SLES 12 FV guest. One of the embedded <add network adapter used> adapters was used in
this testing.
Requirements
• 64 bit SLES 12 SP3 or SLES 11 SP4 host
• 4 CPU cores, minimum
• 8 GB of RAM minimum, plus 256 MB of RAM for each addition CPU (if > 4 cores) on the base system.
• At least 10 GB of hard disk space for the host operating system.
• 30 GB hard disk space for each KVM guest on the root partition.
• A Virtual Machine with maximum configuration (VMM guest) must be tested prior to the multiple VM guest
testing.
• 3 virtual machines minimum. Choose from SLES 12 SP3, SLES 11 SP4, or Windows OS.
• For a fourth or fifth KVM guest add an additional CPU and an additional 768 GB of RAM for each,
minimum.
5.1 Configuring the KVM server

The following instructions are an overview to set up and configure the KVM server on the SUT.
1 Install 64 bit SLES base system as currently documented in section 2.3.1, “Installing SLE on SUT through PXE”,
do not select virtualization or Xen packages.
2 Configure networking as currently documented.
110 Kernel-based Virtual Machine Tests

3 Once the base system is installed, open a terminal type yast2 <Enter>.
4 For SLES 11 SP4 select 'Virtualization' in left panel of the Groups listing. For SLES 12 SP3 continue to the next
step.
5 Select 'Install Hypervisor and Tools'.

6 For SLES 11 SP4 select 'KVM' checkbox in prompt then click on Accept. For SLES 12 SP3 select 'KVM Sever &
KVM Tools' then click on Accept.
7 Click 'install' for additional packages that are required. The original installation source will be needed.
8 Click 'yes' to configure default bridge.
9 Click 'ok'.
10 Exit yast2.
11 For SLES 12 SP3 when PCI Pass-through or SR-IOV is supported, then add intel_iommu = on to the boot loader,
yast2 -> boot loader -> kernel. Edit the kernel line to include intel_iommu = on. Reboot.
12 For SLES 11(latest support pack) reboot system to load kvm drivers.
5.2 Installing a Kernel-based Virtual Machine

The following instructions enable you to install a kernel-based virtual machine (KVM Guest) on the SUT.
1 Log in as root.
2 Enter the password (suse). This install is supported on SLE 11 and SLES 12 SP3. There is a new installation
method which can be used with SLES 12 SP3. See section 5.2b Installing a KVM Virtual Machine with VM
wizard for the new SLES 12 SP3 installation method.
3 Open a terminal window by right-clicking on the desktop, then select Open in Terminal.
4 Type vm-install <Enter>.
5 Click Forward.
6 Select I need to install an operating system.
7 Click Forward.
8 Click on the type of operating system which needs to be installed.
_____________________________________________________________________________________________
Note: Only SLES 12 SP3, SLES 11 SP4, Windows 2008/2012 (latest SP) are supported for certification testing.
_____________________________________________________________________________________________
9 Click Forward.
10 Name the virtual machine.
10a Click Name of Virtual Machine.
10b Enter a unique name for the virtual machine.
10c Click Apply.
11 Configure the Hardware.

11a Click Hardware.
11b For the VMM guest configure up to the maximum RAM of what the hardware product supports. For the 3
virtual machine guests configuration change the initial memory and maximum memory to ¼ of the total
memory in SUT or divided accordingly between the host and all of the guests. Minimum of 1024. Maximum
of 16 GB of memory for 32 bit guest OS.
11c For the VMM guest configure as many CPU's as available. For SLES 11 hosts configure ¼ of the logical
to determine the number of processors to assign to each of the 3 virtual machines. This table does not
apply to the VMM guest.
________________________________________________________________________________________
________________________________________________________________________________________
SLES 11 SP4 1/3 of 2x of the total logical processors in SUT. Minimum of 1 processor up to a
maximum of 64 processors. Note: Each guest should not have more vcpus than
there are lcpus.
there are lcpus.
Windows Server 1/3 of 2x of the total logical processors in SUT. Minimum of 1 processor up to a
maximum of what is allowed by the Windows license. Note: Each guest should
not have more vcpus than there are lcpus.
________________________________________________________________________________________
11d Click Apply.

12 Click Disks.
13 Click Edit (first ensure that the hard disk is highlighted).
13a Change the hard disk for the first KVM guest to be file:/home/vm1/disk0.raw. If this is the second KVM
guest then change the hard disk for the second KVM guest to be file:/home/vm2/disk0.raw. If this is the third
KVM guest then change the hard disk for the third KVM guest to be file:/home/vm3/disk0.raw and so on.
Follow this pattern for any additional KVM guests.
14 Change the size to be 30.0 GB in the Size field (at least 30 GB will be needed, 40 GB for Win 2012).
15 Ensure that the “Create sparse image file” is not checked.
16 Click OK.
17 Click Apply.
18 Configure the Network Adapters.
18a Click Network Adapters.
18b Click edit.
18c In the Type field select the NIC. For SLES make sure the type is “QEMU Virtualized NIC Card” and
br0 is selected for the source. For Windows 2008/2012 leave the default network adapter in the Type field.
The pass-through and SRIOV configuration will use source br1. Change the source from br0 to something
other then br1, use br2, or br3, etc if they are available on Windows 2008/2012 (10.1.x.x network).
_______________________________________________________________________________________
Note: This may change depending on your support of PCI Pass-Through and the number of network adapters

in the SUT.
_______________________________________________________________________________________
18d Click apply.

18e Click apply.
19 Multiple types of installs are available for the KVM guest. The OS can be installed over the network from the
ISO images on TC, or from a DVD or a combination. The install sections below are the instructions for the
different installs.
For a SLES OS Network installation do the following (Recommended):

2 Click the PXE Boot radio button. The installation will access TC for the installation source files.
3 Click Apply.
4 Click OK.
5 The Guest will display a PXE menu which includes the option "SUSE SCK Menu" .
6 Select the "SUSE SCK Menu" option and press "Enter".
7 The SUSE SCK Menu will display the different SLES operating systems that the user may choose to install. If the
SUSE SCK Menu does not display the desired SLES operating system, then repeat the steps in
Section 2.2.3, “Setting up the DHCP/PXE server on TC” then Section 2.2.4, “Adding ISO images to the PXE menu
on TC”.
8 Choose a SLES OS install with a single disk description then press <Enter>. This OS name should be the same OS
and architecture as selected in step 8 when the type of operating system was chosen.
Example: SLES11_SP4x86_64 single disk automated install
9 The SLES OS installation will begin. When the OS installation completes then follow the steps in ”Section 2.4,
“Installing the Test Kit on the SUT”.
For DVD media OS installation do the following:
1 Insert the OS installation DVD into the system.

3 Select Virtual Disk.
4 Click Add.
5 The DVD path should be selected by default. It should be something like phy:/dev/dvd. If it is not correct type in or
browse to the path of the DVD-ROM drive (example: /dev/dvd or phy:/dev/dvd).
6 Click OK.
7 Click Apply.
8 Click OK.
9 Please refer to the appropriate section for the KVM installation:
• Section 6, “Manually Installing SLES 12 SP3 or SLES 11”

• Section 5.3, “Installing a Windows 2008, 2008 R2, or 2012 Kernel Virtual Machine”
5.2b Installing a KVM Virtual Machine with SLES 12 SP3 VM wizard

For SLES 12 there is a new VM wizard. The New VM wizard helps you through the steps required to create a virtual
machine and install its operating system.
1 In a terminal type yast2 <Enter>.

2 Select “Virtual Machine Manager”, then choose Administrator Settings (Yast2).
3 Select the Monitor icon in the upper left (Create a new virtual machine).
4 Select “Network Boot (PXE)” then click Forward.
5 Make sure the “OS Type” and “Version” are correct (either SLES 12, SLES 11 or windows), then click Forward.
6 Configure the memory (RAM) and the CPU's.
6a For the VMM guest configure up to the maximum RAM of what the hardware product supports. For the 3 virtual
machine guests configuration change the initial memory and maximum memory to ¼ of the total memory in SUT
or divided accordingly between the host and all of the guests. Minimum of 1024. Maximum of 16 GB of memory
for 32 bit guest OS.
6b For the VMM guest configure as many CPU's as available. For SLES 11 hosts configure ¼ of the logical
to determine the number of processors to assign to each of the 3 virtual machines. Then click forward. This
table does not apply to the VMM guest.
________________________________________________________________________________________
________________________________________________________________________________________
there are lcpus.
there are lcpus.
Windows Server 1/3 of 2x of the total logical processors in SUT. Minimum of 1 processor up to a
maximum of what is allowed by the Windows license. Note: Each guest should
not have more vcpus than there are lcpus.
________________________________________________________________________________________
7 Change the size to be 30.0 GB in the GiB size field (at least 30 GB will be needed, 40 GB for Win 2012). Then click
forward.
8 Enter a unique VM name.

9 Select “Network selection”, then choose the “Bridge” from the drop down menu for the PXE network (e.g. Bridge
br0: Host device eth0).
10 Click on Finish.

11 The OS installation will begin. Start at step 6 in Section 2.2.6, “Configuring the SUT for and using the PXE boot”.
Return to this section after completing Section 2.3.1, “Installing SLE on SUT through PXE”. The GUI will have
failed to start, You will be in a terminal window (e.g. TTY2).
12 Login, then run "sax2". Click "Ok" in the sax2 popup window. Then run "init 5" to bring up the GUI.
13 If the Test Kit installation automatically occurs after the OS install, then follow the steps in Section 5.5,
“Configuring KVM for the PCI Pass-Through” for one of the VM guests. Otherwise follow the steps in ”Section
2.4, “Installing the Test Kit on the SUT”.
14 Repeat for each guest installation.
5.2c Automated Installation of a KVM Virtual Machine

We provide a script that automates installing SLES 11 VM's and 12 VM's on SLES 11 hosts and 12 hosts running the
XEN or KVM hypervisor. The script leverages the existing PXE/DHCP server and autoyast files on TC. The script
detects the host's SLES version and hypervisor and calls vm-install or virt-install as appropriate. The script can be run
with or without passing paramters. The script is located on SUT at /opt/suse/testKits/system/bin/
Starting the script without passing parameters.

When starting the script without passing parameters it will present a menu of SLES releases to choose for the VM.
Then the VM name, amount of RAM, disk location, and number of vCPUs can be specified. Next, the script takes
care of the rest of the installation details. To see which ISO's are available on TC run the script without any options.
On SUT use the command:
/opt/suse/testKits/system/bin/install_vm
Starting the script with passing parameters.

The VM install can be completely unattended by passing parameters to "install_vm" script indicating the number of
VMs to install and the location for VM(s) disk storage. The script calculates CPU and Memory available on the host
and assigns 80% of memory and all vcpus to one Max VM (when installing one VM) or divides memory and vcpus
equally among VMs when installing multiple VMs. Before starting installation, the script presents a summary of VM
to be installed and allows the user to change any or all settings for each VM if necessary. The script determines the
VM OS release to be installed based on existing ISO's, and autoyast files on TC. vCPUs in multiple VM installs will
be overcommited by a factor of 2x, this number can vary depending on whether hyperthreading is enabled.
Please change to the /opt/suse/testKits/system/bin/ before trying the examples.

This example will install one Max VMM and create a storage pool in directory /home:
./install_vm -c 1 -p /home
This example will install 3 VMs, create a storage pool in /data dir, and leave enough resources for one future VM:
./install_vm -c 3 -p /data -w 1
For script help, details, requirements and known issues please use -h option:
/opt/suse/testKits/system/bin/install_vm -h
5.3 Installing a Windows 2008, 2008 R2, or 2012 Kernel Virtual Machine
1 Follow the prompts to install Windows with the default typical settings. Ensure that the latest support packs are
being used.

2 We suggest using the following IP addresses.
________________________________________________________________________________________
____________________________________________________________________________________________
VM Guest 1 10.1.1.11
VM Guest 2 10.1.2.12 (If supported by the NIC, this VM is used for PCI
Pass-through /SRIOV)
VM Guest 3 10.1.1.13
VM Guest 4 10.1.1.14
Windows VM Guest 5 (optional) 10.1.1.15
____________________________________________________________________________________________
________________________________________________________________________________________
Note: To send keystrokes to the Windows 2008 VM use the send key drop down located at the top of the VM
window to select the keystrokes.
________________________________________________________________________________________
3 Be sure to disable (turn off) all firewalls (domain, private, public).

4 Install the Virtual machine driver pack for Windows onto the Xen/KVM Windows guest.
For Windows 2008, ad 2012 server Virtual machine driver pack go to:
For SLES 11 SP4, SLES 12 and later:

5 Change the default network adapter to virtio. Shut down the windows guest, change the network adapter to virtio
then boot the guest.
6 The virtualization documentation for SLES is available online.

https://www.suse.com/documentation/sles11/

7 Continue to Section 5.4, “Installing the Test Kt on the Windows Virtual Machine”.
5.4 Installing the Test Kit on the Windows Virtual Machine

1 Verify Samba is running on TC (must be performed if TC is rebooted)

1a On the TC terminal type /etc/init.d/smb status <Enter>.
1b If the status is “running” then Samba is running. Otherwise start Samba by typing: /etc/inint.d/smb start
<Enter> at the command prompt or reboot TC.
2 Set the static IP address on the Windows VM.

2a On Windows Server 2008 right click on local area network connection in taskbar, click on Network and
Sharing Center then click “Manage Network Connection” link.
2b On Windows 2012:
2b1 Press the windows key. If the windows key is not working then click on the the Virtual hardware details
button (it looks like a blue circle with an “i”) at the top. Select display, then select VNC. Select the key map
to be en-us. Click Apply.
2b2 Click on Control Panel.
2b3 Click on View Network Status + Tasks.
2b4 Click on Ethernet (next to connections).
2c On Windows Server 2008 right click on Local Area Connection, then select Properties.
2d For Windows Server 2008 and 2012 click on Internet Protocol Version 4 (TCP/IPv4) -> Properties.
2e Click on Use the following IP address.
2f Enter the IP address (e.g. 10.1.1.15). The windows IP address may also need to be changed in the test project on
TC.
2g Enter the Subnet mask (e.g. 255.255.255.0).
2h Enter the default gateway for the KVM host (e.g. 10.1.1.1).
2i Click on OK -> Close.
2j Click on Close Or X to close the Network Connection and Network Sharing Center.
3 Map drive T: to \\<IP address of TC>\windir\.
3a Click on Start -> Computer on Win2008.
3b On Win 2012 press windows button+e, then click computer, then choose Map Network Drive → Map Network
Drive (again).
3c On Win 2008 click on Tools -> Map Network Drive.
3c Select Drive T:
3d Type \\<IP address of TC>\windir\ (e.g. \\10.1.1.2\windir\)
3e Click finish.
3f Enter the TC username (root) and password (suse).
4a Right click on "Start", select "Explore".
4b Right Click on "Local Disk(C:)", Select "Share..."
4c Click the "Advanced Sharing..." button.
4d Check the "Share this folder" box, then click the "OK" button.

4e Click the "Network and sharing center" link.
4f Click the "Public Flocer Sharing" pull down menu arrow.
4g Click the "Turn on sharing so anyone with network access can open files" radio button,
4h Click the apply button.
5a Press the window button + e to open Windows Explorer.
5b Right click on "Local Disk(C:)", select "Share with".
5c Click on "Advanced Sharing".
5d Click on the “Advanced Sharing” button.
5e Check the "Share this folder" box, then click the "OK" button.
5f Click the "Network and Sharing Center" link.
5g Click on the All Networks Arrow to expand the section.
5h Click the "Turn on sharing so anyone with network access can open files" radio button.
5i Click the “Turn off password protection sharing...” radio button.
5j Click Save Changes.
5k Click Close.
6 Run Tclink on the Windows VM.

6a Double click the following file: T:\testKits\system\bin\XpClient.bat.
In Windows 2012, this file will be locatable in the Windows Explorer window used in step 3 above.
6b Click Run.
7 To install another Xen virtual machine return to Section 5.2, “Installing a Kernel Based Virtual Machine” step 4,
Otherwise begin in Section 5.5, “Configuring KVM for Network PCI Pass-through” Or begin in Section 5.6,
“Configuring KVM for SR-IOV”.
5.5 Configuring KVM for Network PCI Pass-Through

We require that SR-IOV be tested on SLES versions after SLES 11 SP4 during Yes Certification if the NIC supports it.
If your NIC supports SR-IOV with SLES 12 SP3 then go to section 5.6 Configuring KVM for SR-IOV. Network PCI
Pass-Through can be tested if SR-IOV is not supported. PCI Pass-through and SR-IOV are optional on SLES 11 SP4
during Yes Certification. This section provides the steps to configure Network PCI Pass-Through on a KVM guest.
Network PCI Pass-Through requires one of the embedded network adapters should be used as the pass- through
adapter, but an additional add-on Network PCI Pass-Through adapters can be added and used then noted on the
submission. The Test Kit defaults to use VM2 for the PCI Pass-Through.
1 If the host system is Intel processor-based then host must be booted with the following boot parameter:
intel_iommu=on. To add intel_iommu=on to the boot loader Click Applications menu → System Tools →
Yast → Boot Loader → Kernel Tab, then edit the kernel line.
____________________________________________________________________________________________
Note: If the host system is AMD processor-based you will not need the intel_iommu boot parameter but you will

Boot the system.
____________________________________________________________________________________________
____________________________________________________________________________________________
Note: In addition to steps below we provide a script that automates the steps for assigning a NIC via PCI Pass-
through or SR-IOV (VF NIC) to a VM. You may run the script on SUT with command:

___________________________________________________________________________________________
2 Select a device to reassign to a fully virtualized VM Guest. To do this run “lspci | grep Ethernet” on a terminal in
the host and determine the device number. For example, if lspci contains the following line:
06:00.1 Ethernet Controller: Intel Corporation I350 Gigabit Ethernet Controller then the PCI number is 6:00.1.
____________________________________________________________________________________________
Note: During standard certification two network adapters or ports are required. The adapter being passed through
to the virtualized guest should be one of the embedded adapters in the system or also be an “additional” adapter or
chipset beyond the original two adapters in the system. This additional network adapter should not be configured in
the host system, it will be passed through to the guest then configured in the guest.
____________________________________________________________________________________________
3 Start the Virtual Machine Manager on the system host: Yast → Virtualization → Virtual Machine Manager
4 Close Yast.
5 If the SLES guest you will be passing the network adapter to is running it should be shutdown.
6 Once the guest is grayed-out (shutdown) in the Virtual Machine Manager you can proceed with the configuration.
7 Right click on the greyed-out guest in the Virtual Machine Manager and select Open. (Do not start the guest OS)
8 Select View then select Details.
9 Remove the existing virtual network adapter (e.g., NIC :59:3c:f5), right click on the adapter then select “– Remove
Hardware” or highlight and click “-Remove”. Select “Yes” when prompted “Are you sure you want to remove this
device?”.
10 Click the “+ Add Hardware” button in the lower left corner.

11 Select “PCI Host Device” from the left side menu options.
12 Scroll through the “Host Device” list until you find the adapter that will be passed through; for example “06:00.1
Ethernet Controller: Intel Corporation I350 Gigabit Ethernet Controller ”
13 Select the adapter in the list then click Finish.

___________________________________________________________________________________________
Note: The pass-through LAN adapter hardware should be physically cabled to the second network test hub (e.g.,
10.1.2.x network) and the IP address will be 10.1.2.x.
___________________________________________________________________________________________

14 From the menu options at the top guest select View and change Details back to Console.
15 Boot the guest and login.
16 From a terminal in the guest run “lspci” to validate the pass-through adapter is present. Run “yast2 lan” from the
terminal command prompt. The passed through network adapter should be available in the guests Network
Settings, Overview tab.
___________________________________________________________________________________________
remove it.
___________________________________________________________________________________________
17 Now select the network adapter that has been passed through to the guest, click edit and configure it with the IP
address 10.1.2.12 and Subnet Mask 255.255.255.0. Change the VM3 10.1.3.1 IP address in the test project to
become 10.1.2.12.
18 Click Next then OK to save the pass-through adapters network configuration. The pass-through network adapter
should now be assigned directly to and functioning in just that guest; you may want to validate with the network
connection with a ping from the pass-through guest to another system.
___________________________________________________________________________________________
Note: ntp time synchronization may need to be restarted on the guest; “/etc/init.d/ntp restart” will reset ntp if
needed.
___________________________________________________________________________________________
19 If the Test Kit was installed on the VM prior to PCI Pass-Through NIC assignment, then run
20 To install another KVM virtual machine return to Section 5.2, “Installing a Kernel Based Virtual Machine” step 4,
otherwise begin testing in Section 2.5, “Updating the Products.txt File”.
5.6 Configuring KVM for SR-IOV

We require Network SR-IOV to be tested on SLES versions after SLES 11 SP4 during Yes Certification.
If Network SR-IOV is not supported then please test PCI Pass-Through. This section provides the steps to configure
SR-IOV on a KVM guest. We recommend that one of the embedded network adapters be configured SR-IOV, but an
additional adapter can be added and used for SR-IOV then noted on the submission. If SR-IOV is chosen, then one of
the embedded network adapters should be used as the SR-IOV adapter, but an additional SR-IOV adapter can be
added and used then noted on the submission.
Requirements
• SR-IOV-capable network card (as of SUSE Linux Enterprise Server 12 network cards support SR-IOV)
• x86_64 host supporting hardware virtualization (AMD-V or Intel VT-d)
_______________________________________________________________________________________


_______________________________________________________________________________________
1 In the system BIOS, enable the virtualization (example Intel vt-d).

2 Enable iommu in the hypervisor (e.g. add boot parameter intel_iommu=on on the linux commandline of the host) at
boot. Reboot after adding this to the command line. If the host system is AMD processor-based you will not need
the intel_iommu boot parameter but you will need to make sure the IOMMU extension is set to “on” or “enabled” in
the system setup utility before proceeding.
3 Verify that the NIC driver supports sr-iov by opening a terminal then typing "lspci -v | more" then scroll to your
network device. A device that supports SR-IOV reports a capability similar to the following:
Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV).
4 Check whether the SR-IOV driver is already loaded by running lsmod | egrep "^be2net ". In the following example
a check for the be2net driver (Emulex OneConnect 10Gb NIC) returns a result.
Be2net 120836 0
If the driver is loaded, unload it
modprobe -r be2net
5 Load the SR-IOV driver with the VFs parameter. For example for be2net driver:
modprobe be2net num_vfs=2
To find out the correct VFs parameter for your driver, issue command "modinfo <drivername>" and look at "parm:"
sections.
6 Run "lspci | grep Ethernet" command and verify additional Virtual NICs were created. This may require rcnetwork
restart to re-initialize the network.
7 Make loading NIC driver with VFs parameter persistent by adding the VFs driver option to /etc/modprobe.d/99-
local.conf file. For example, from a terminal command line for be2net driver run:
echo "options be2net num_vfs=2" >> /etc/modprobe.d/99-local.conf
and then run command "mkinitrd" to refresh the driver configuration.
8 Reboot the machine and check if the SR-IOV driver is loaded.

9 Once the SR-IOV hardware is properly set up on the VM Host Server, you can add VFs (virtual functions) to VM
Guests. In order to do so, you need to collect some data first.
_____________________________________________________________________________________________
Note: The following procedure is using example data. Make sure to replace it by appropriate data from your setup.
_____________________________________________________________________________________________

Lspci | grep Ethernet <Enter>
0c:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 10)
10 Use the virsh nodedev-list command to get the PCI address of the VF (virtual function) you want to assign and it's
corresponding PF (physical function). Numerical values from the lspci output shown above. Load and configure
the SR-IOV Host drivers (for example 01:00.0 or 04:00.1) are transformed by adding the prefix "pci_0000_" and
by replacing colons and dots with underscores. So a PCI ID listed as "04:00.0" by lspci is listed as
"pci_0000_04_00_0" by virsh. The following example lists the PCI IDs for the second port of the Intel 82576NS
network card:
~ > virsh nodedev-list | grep 0000_0c_08_

pci_0000_0c_08_0
pci_0000_0c_08_1
The first two entries represent the PFs whereas the other entries represent the VFs.
11 Get more data that will be needed by running the command virsh nodedev-dumpxml on the PCI ID of the VF you
want to add:
~ > virsh nodedev-dumpxml pci_0000_04_10_0

<device>
<name>pci_0000_0c_08_0</name>
<path>/sys/devices/pci0000:00/0000:00:01.0/0000:0c:08.0</path>
<parent>pci_0000_00_01_0</parent>
<driver>
<name>be2net</name>
</driver>
<capability type='pci'>
<domain>0</domain>
<bus>12</bus>
<slot>8</slot>
<product id='0x0710'>OneConnect 10Gb NIC (be3)</product>
<vendor id='0x19a2'>Emulex Corporation</vendor>
<capability type='phys_function'>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/>
</capability>
<iommuGroup number='54'>
</iommuGroup>
</capability>
</device>

The following data is needed for the next step:
<domain>0</domain>
<bus>11</bus>
<slot>16</slot>
12 Create a temporary XML file (for example /tmp/vf-interface.xml containing the data necessary to add a VF
network device to an existing VM Guest. The minimal content of the file needs to look like the following:
<interface type='hostdev' managed = 'yes'> (See A below)

<source>
<address type='pci' domain='0' bus='11' slot='16' function='0'/> (See B below)
</source>
</interface>
_______________________________________________________________________________________
Note A: VFs do not get a fixed MAC address, it changes everytime the host reboots. When adding network
devices the "traditional" way with <hostdev>, it would require to reconfigure the VM Guest's network device
after each reboot of the host, because of the MAC address change. To avoid this kind of problems, libvirt
introduced the "interface type='hostdev'" directive, which sets up network specific data before assigning the
device.
Note B: Specify the data you acquired in the previous step here.
_______________________________________________________________________________________
13 Last, add the VF interface to an existing VM Guest. With the guest running, you may list and find their IDs with
command "virsh list"
linux-s46s:~ # virsh list

Id Name State
----------------------------------------------------
2 sles11 running
3 sles12-x86_64 running
virsh attach-device GUEST /tmp/vf-interface.xml --config
virsh attach-device sles12-x86_64 /tmp/vf-interface.xml --config
where GUEST is the name or ID of the guest

--config
This option will only affect the persistent XML, even if the domain is running. The device will only show up in
the guest on next boot.
14 Shutdown guest VM and re-start for new configuration with SR-IOV card to take effect. The new adapter can be
verified in view → details. The old virtual network driver must be deleted.
15 Go to yast2 lan on the guest and select the network adapter that has been passed through to the guest, click edit and
configure it with the IP address 10.1.2.x and Subnet Mask 255.255.255.0.
____________________________________________________________________________________________

Note: If the virtual network adapter is still listed in Yast – Network Settings, click on it then click Delete to remove
it.
____________________________________________________________________________________________
16 If the Test Kit was installed on the VM prior to SR-IOV NIC assignment, then run
17 To install another KVM virtual machine return to Section 5.2, “Installing a Kernel Based Virtual Machine” step
4, Otherwise begin testing in Section 2.5, “Updating the Products.txt File”.
___________________________________________________________________________________________
Note: Some network cards such as Intel 82576NS may require a special SR-IOV driver to be loaded. Follow the
instructions of your specific card to load the correct SR-IOV driver.
___________________________________________________________________________________________
5.7 Manually Installing the Test Kit on the SLES KVM Guests
1 On the host, log in as root.

2 Start the KVM.
3 On the TC, log in as root.
4 Open a terminal on TC, then type sck_copy_install_files.sh <Enter>. The file is located in /home/InstSource/sck/.
5 Enter the IP address of the Guest KVM to install the Test Kit onto then press <Enter>.
6 Follow the on screen instructions on the TC. 0The on screen instructions will include which guest VM to run
sck_install.sh.
7 Choose “SUT System” by pressing 1 <Enter>.
8 When prompted, enter the IP address of TestConsole (10.1.1.2).
menu is to confirm or change the assigned IP address information. Change the IP address information as needed by
typing the NIC number (example 1) then <Enter>. Press C <Enter> if the displayed information is correct and all
changes have been made.
11 Close the terminal window by typing Exit <Enter>. This is important.
12 Verify this system has the same time setting as TestConsole.

17 Click Close.
____________________________________________________________________________________________
Note: Time synchronization may take up to 2 hours. After SUT, and TC installations are complete, ensure that the
time is the same on both systems. If the times not are synchronized then see Section A.4, “Time Synchronization”

in the Troubleshooting section of the Appendix.
____________________________________________________________________________________________
18 Install additional KVMs as instructed in Section 5.2, “Installing a Kernel-Based Virtual Machine” or start testing
by beginning in Section 5.8, “Starting the Tests”. The testing section is intended to be followed section by section
until the testing is completed.

After you have set up the test configuration, you are ready to begin the tests.
1 Begin at section Section 2.5, “Updating the Products.txt File”.

en) 6 April 2007

6
Manually Installing SLES 12 or SLES 11
This section discusses manually installing SLES and covers the following topics:
• Section 6.1, “Manually Installing SLES 12 SP3 on SUT”
• Section 6.2, “Manually Installing the Test Kit on the SLES 12 SP3 SUT”
• Section 6.3, “Manually Installing SLES 11 SP4 on SUT”
• Section 6.4, “Manually Installing the Test Kit on the SLES 11 SP4 SUT”
• Section 6.5, “Starting the Tests”
6.1 Manually Installing SLES 12 SP3 on SUT

The LAN adapters in TC must match the highest speed LAN adapter in the SUT.
which will delete any and all existing partitions. For a DVD installation do the following, if this is a PXE manual
installation skip to step 4.
2 Boot the system to SUSE LINUX Enterprise Server 12 (latest support pack) from DVD.

4 If prompted click No to the Network is not configured...message in the Updating the installer screen.
5 Select the English (US) language.
6 Select the English (US) keyboard Layout.
8 If prompted click Next in the Network Settings screen. The network will be set up in the next section during the
Test Kit installation on this SUT.
9 Click the Skip Registration button on the Registration screen.
9a Click OK in the Warning message prompt.
9b Click Next.
10 If prompted click the Next in the Add On Product or Installation Options screen.
11 For a base SLES 12 SP3 install (not KVM or XEN) click Next in the System Role screen. For XEN or KVM click
the appropriate box.
12 For a base SLES 12 SP3 install (not a KVM guest) click Next in the Suggested Partitioning screen. If this
installation is for a SLES 12 SP3 KVM guest follow the steps starting at 12a.
126 Manually Installing SLES 12 or SLES 11

12a Click “Edit Proposal Settings”.
12b Uncheck “Propose Separate Home Partition”.
12c Uncheck “Enable Snapshots”.
12d Click OK.
12e Click Next.
14 Set the system clock to match the time of the other systems on your rack.
14a Click the Other Settings button.
14b Change the Current Time and Current Date to be the same as TC.
14d Click the Next button to complete the setup of the Clock and Time Zone screen.
15a Click the Skip User Creation radio button.
15b Click Next in the Local User screen.
16 Set the password for the System Administrator root.
16b Click Next.
16c Click Yes to really use the password at the password is too simple prompt.
17b Click the Details button.
17c Select the software patterns. Ensure that only the following patterns are checked (all remaining patterns should
be blank):
✔ Base System
✔ AppArmor
✔ 32-Bit Runtime Environment
✔ Minimal System
✔ X Window System
✔ File Server
✔ Printing

17d Click Accept.
17e If prompted, click Continue in the Changed Packages window to accept the automatic changes.
17f If prompted, click Continue in the Changed Packages window to accept the unsupported packages.
18 Disable the firewall by clicking on disable next to firewall will be enabled. The display will change to firewall will
be disabled.
19 If listed, enable the SSH service by clicking on enable next to SSH service will be disabled. The display will
change to SSH service will be enabled.
20 If listed, enable an SSH port by clicking on open next to SSH port will be blocked. The display will change to SSH
port will be open.
21 Click Install to start the installation.
22 Click Install in the popup window to confirm the installation.
23 After the installation is complete remove the DVD from SUT.
24 If this installation was a SLES 12 SP3 Xen Guest (Xen virtual machine) then continue to Section 4.3 “Manually
Installing the Test Kit on SLES Xen Virtual Machines”.
25 If this installation was a SLES 12 SP3 KVM Guest (virtual machine), then go to Section 5.6, “Manually
Installing the Test Kit on the SLES KVM Guests”.
26 If this installation was a SLES 12 SP3 only, a SLES 12 SP3 KVM Host, or a SLES 12 SP3 Xen Host (host server)
proceed to Section 6.2, “Manually Installing the Test Kit on the SLES 12 SP3 SUT”.
6.2 Manually Installing the Test Kit on the SLES 12 SP3 SUT
1 Log in as root. The password created by a PXE automatic install will be suse.
then a loop mount procedure can be used by following the steps below:
2d Type the following in a terminal window: /root/Desktop/sck/sck_install.sh <Enter>. Skip to Step 6 below.
3 If prompted, click Cancel at the What do you want to do? question in the CD-ROM Daemon prompt, or Close CD
Contents Display window.
5 Type /<mount point>/sck_install.sh <Enter>, Example: /run/media/root/CDROM/sck_install.sh.
6 If prompted, remove the Test Kit CD then replace it with the OS DVD which was used to install the SUT.
Then run the Test Kit script file as indicated in the onscreen message. Choose the “SUT System” install, then press
<Enter>. Example: 1 <Enter> for SUT.

7 When prompted, enter the IP address for TestConsole (default = 10.1.1.2) then press <Enter>.
menu is to confirm or change the assigned IP address information. Also to ensure that an existing NIC management
only port is not assigned an IP address for NIC testing. Remove any IP address assigned to the NIC management
only ports by typing/assigning do_not_test. Change the IP address information as needed by typing the NIC
number (example 1) then press <Enter>. Press C <Enter> if the displayed information is correct and all changes
have been made.
13 Right-click on the speaker in the bottom right of the Display panel.
14 Click on the round button which has the screw driver and the wrench inside.
15 Click Date and Time.
16 Select AM/PM in the drop down box next to Time Format.
17 Click on the x in the upper right corner to Close the window.
18 Remove the DVD.
information).
20 If this installation was a SLES 12 SP3 Xen Host (host server) then to return to Section 4.1, “Installing a Xen
Virtual Machine”.
21 If this installation was for a SLES 12 SP3, and TC is configured, then go to Section 6.5, “Starting the Tests”.
22 If this installation was for a SLES 11 SP4 KVM Host then then go to Section 5.1, “Configuring KVM server”.
23 If this installation was a SLES 12 SP3 fully virtualized VM and the PCI Pass-Through has not been configured on
a SLES 12 SP3 fully virtualized VM then goto Section 4.4, “Configuring Xen for the PCI Pass-Through”.
6.3 Manually Installing SLES 11 SP4 on SUT

The LAN adapters in TC must match the highest speed LAN adapter in the SUT.
which will delete any and all existing partitions.
For a DVD installation do the following, if this is a PXE manual installation skip to step 4:
2 Boot the system to SUSE LINUX Enterprise Server 11 SP4 from DVD.

4 Select the English (US) language.
5 Select the English (US) keyboard Layout.
7 If prompted with the check media screen click Next.
8 Select New Installation, then click Next.
10 Set the system clock to match the time of the other systems on your rack.
10a Click the Change button below and to the right of Time and Date.
10b Change the Current time and Current date.
11 Click the next button to complete the setup of the Clock and Time Zone screen.
12 Select the Physical Machine scenario, then click Next.
_______________________________________________________________________
Note: The Physical Machine also applies to all Xen VM installations and KVM install.
_______________________________________________________________________
13 Create partition for first hard disk or hardware RAID.
13b Select the hard disk or hardware RAID that you want the OS installed on.
13c Click Next.
13d Click Use entire hard disk (This is the default if the Hard disk is empty).
13e Click Next.
14 (If you have only one hard disk or hardware RAID, the defaults are okay. Proceed to step 15.) Create partitions on
all remaining hard disks.

14b Click Custom Partitioning for experts in the Preparing Hard Disk screen and click Next.
14c Select Hard Disks or hardware RAID in the System View window and select the disk you want to partition.
14d Click the Add... button at the bottom of the Hard Disk: window.
14e Click the Primary partition radio button.
14f Click Next to accept the primary partition.
14g Click Next to accept the Maximum Size as the new partition size. Ensure that is maximum size, not custom.
14h Assign a mount point to the hard drive or hardware RAID device. The following suggestions may be used for
the mount points:
• For a hard drive, change the mount point to /media/tc/hdx where x= the number of the hard disk (e.g. hd2,
hd3, hd4, ..., hd16) TestConsole uses HD1 for the first hard disk.

• For a RAID, change the mount point to /media/tc/raidx where x= the number of the hardware RAID array
(e.g. raid2, raid3, ..., raid16) TestConsole uses hardware RAID1 for the first hard disk.
14i Click Finish to create the primary partition formatted with ext3 for the entire disk space.
14j Repeat these steps (14c-14i) for each device that hasn't been partitioned.
14k Click Accept to return to the Installation Settings screen.
15b Click Details.
15c Click on the Patterns Tab.
15d Select the software patterns. Ensure that only the following patterns are checked (all remaining patterns
should be blank):
✔ Base System
✔ 32-Bit Runtime Environment (only listed for 64-bit install)
✔ Xen Virtualization Host (if you are going to test the Xen host OS)
✔ Minimal System
✔ X Window System
✔ File Server
✔ Print Server
✔ Xen Virtual Machine Host Server (if you are going to test the Xen host OS)
15e Click on the Search Tab.
15f In the Search box, type bonnie, then click the Search button.
15g Check the bonnie package for installation.
15h In the Search box, type kexec-tools, then click the Search button.
15i If unchecked, check the kexec-tools package for installation.
15j In the Search box, type makedump, then click the Search button.
15k If unchecked, check the makedump package for installation.
15l In the Search box, type mgetty, then click the Search button.
15m Check the mgetty package for installation.
15n In the Search box, type vsftpd, then click the Search button.
15o If unchecked, check the vsftpd package for installation.
15p In the Search box, type nmap, then click the Search button.
15q Check the nmap package for installation, then click Accept.

15r Click Accept in the Yast2 agfa-fonts window.
15s If prompted, click Continue in the Changed Packages window to accept the automatic changes.
15t If prompted, click Continue in the Changed Packages window to accept the unsupported packages.
15u Click Install to start the installation.
15v Click Install in the YaST2 window to confirm the installation.
16 The OS file copy will begin.
16a Change SLES DVD if prompted.
16b After package installation completes, the system will restart.
________________________________________________________________________________________
Note: During the SLES 11 SP4 Xen Guest (VM) install, the SLES 11 SP4 Xen Guest (VM) window may be
closed after restart. Use the virtual machine manager in YAST2 to open the partially installed SLES 11 SP4
VM. The SLES 11 SP4 Xen Guest (VM) install will continued as normal. If needed <Ctrl-Alt> can be used to
gain mouse pointer screen access. For more information about the virtual machine manager see the Xen
documentation.
________________________________________________________________________________________
17 Set the Password for user root.
17b Click Next.
17c Click Yes to really use the password at the Password too simple prompt.
17d Uncheck Change Hostname via DHCP.
17e Edit the host name (e.g., SUT).
The following Host names examples(No spaces allowed in the name) can be used for the Host Name field on
each correlating machine:
• TC—TestConsole
• Client—Client
• SUT—System_Under_Test
• Guest 1—VMGuest1 (en) 6 April 2007
• Guest 2—VMGuest2
• Guest 3—VMGuest3
17f Edit the Domain name (e.g., suse.com).
17g Click Next at the Hostname and Domain Name window.
18 Disable the firewall by clicking on disable next to firewall is enabled. The display will change to firewall is
disabled.
19 Configure the Network.
19a Click Network Interfaces in the Network Configuration window.
19b Select the Network Bridge if installing Xen or Select the NICs if installing a SLES 11 SP4 base system. Note
that a VM may list a Virtual Ethernet Card as the NIC.
19c Click edit.

19d Click the Statically assigned IP Address radio button.
19e Enter an IP address.
You can configure up to 8 NICs. Use the following table for IP addresses.
________________________________________________________________________________________
System IP Address
____________________________________________________________________________________________
SUT (NIC 1) 10.1.1.1
SUT (NIC 2) 10.1.2.1
SUT (NIC 3) 10.1.3.1
...
SUT (NIC 8) 10.1.8.1
____________________________________________________________________________________________
If configuring a Xen SLES 11 SP4 Host (Dom 0), please use the following IP addresses.
________________________________________________________________________________________
System IP Address
____________________________________________________________________________________________
SUT (NIC 1) Not configured
...
Network Bridge (NIC 1) 10.1.1.1
...
____________________________________________________________________________________________
If configuring a Xen Guest (virtual machine) or a KVM Guest, please use the following IP addresses for the
guests.
________________________________________________________________________________________
____________________________________________________________________________________________
VM Guest 1 10.1.1.10
VM Guest 2 10.1.1.11
VM Guest 3 10.1.1.12
VM Guest 4 10.1.1.13
____________________________________________________________________________________________
19f Edit the Subnet mask, if necessary. 255.255.255.0 should be used for all NICs. The hostname should be left
blank.
19g Click Next to return to the Network Settings window. If prompted, click yes at the “really leave hostname
blank?” prompt.
19h Repeat steps 19b-19g for each NIC.

19i Do not enable IP forwarding. If this is a Xen guest then the Gateway Address of 10.1.1.1 is needed.
19j Click OK in the Network Settings window.

19k Click Next in the Network Configuration window.
19l When prompted, click No, Skip This Test radio button in the Test Internet Connection window.
19m Click Next on the Test Internet Connection window.
19n Click Next to use the existing configuration in the Network Services Configuration window.
20a Ensure the Local (/etc/passwd) radio button in the User Authentication Method window is selected.
20b Click Next in the User Authentication Method window.
20c Click Next in New Local User window.
20d Click Yes at the warning about the Empty user login.
21 Click Next at the Release Notes window.
22 Click Next at the Hardware Configuration window.
23 Uncheck Clone this system for Autoyast.
24 Click Finish at the Installation Completed screen.
25 Remove the DVD from SUT.
26 If this installation was a SLES 11 SP4 Xen Guest (Xen virtual machine) then continue to Section 4.3 “Manually
Installing the Test Kit on SLES Xen Virtual Machines”.
27 If this installation was a SLES 11 KVM Guest (virtual machine), then go to Section 5.6, “Manually Installing the
Test Kit on the SLES KVM Guests”.
28 If this installation was a SLES 11 SP4 only, a SLES 11 SP4 KVM Host, or a SLES 11 SP4 Xen Host (host server)
proceed to Section 6.4, “Manually Installing the Test Kit on the SLES 11 SP4 SUT”.
(en) 6 April 2007
6.4 Manually Installing the Test Kit on the SLES 11 SP4 SUT
1 Log in as root. The password created by a PXE automatic install will be suse.
then a loop mount procedure can be used. Copy the iso onto the SUT. Mount the iso image on the SUT by typing in
a terminal: mount /<Path>/<iso file name.iso> /mnt <Enter>. Then on SUT type: /mnt/sck_install.sh <Enter>.
3 If prompted, click Cancel at the What do you want to do? question in the CD-ROM Daemon prompt, or Close CD
Contents Display window.

5 Type /<mount point>/sck_install.sh <Enter>, Example: /media/CDROM/sck_install.sh.
6 When prompted remove the Test Kit DVD then replace it with the OS DVD which is installed onto the SUT. Then
run the Test Kit script file as indicated in the onscreen message. Choose the “SUT System” install, then press
<Enter>. Example: 1 <Enter> for SUT.

8 When prompted, enter the password for TestConsole (i.e. suse) then press <Enter>.
menu is to confirm or change the assigned IP address information. Also to ensure that an existing nic management
only port is not assigned an IP address for NIC testing. Remove any IP Address assigned to the NIC management
only ports by typing/assigning do_not_test. Change the IP address information as needed by typing the NIC
number (example 1) then press <Enter>. Press C <Enter> if the displayed information is correct and all changes
have been made.
17 Click Close.
18 Remove the DVD.
information).
20 If this installation was a SLES 11 SP4 Xen Host (host server) then to return to Section 4.1, “Installing a Xen
Virtual Machine”.
21 If this installation was for a SLES 11 SP4 SUT, and TC is configured, then go to Section 6.5, “Starting the Tests”.
22 If this installation was for a SLES 11 SP4 KVM Host then then go to Section 5.1, “Configuring KVM server”.
23 If this installation was a SLES 11 SP4 fully virtualized VM and the PCI Pass-Through has not been configured on
a SLES 11 SP4 fully virtualized VM then goto Section 4.4, “Configuring Xen for the PCI Pass-Through”.

After you have set up the test configuration, you are ready to begin the tests.
1 Begin at section Section 2.5, “Updating the Products.txt File”.

en) 6 April 2007

A
Troubleshooting and Help
• Section A.1, “Installation Issues”
• Section A.2, “Installing SLES on TC”
• Section A.3, “TestConsole”
• Section A.4, “Time Synchronization”
• Section A.5, “Component Check Issues”
• Section A.6, “Validate Install Test, Component Check, and Get Test Logs”
• Section A.7, “Get Test Logs Test”
• Section A.8, “Video Test and Desktop Effects Testing Issues”
• Section A.9, “Serial Port Test”
• Section A.10, “Stress Tests”
• Section A.11, “Test Kit Installation Issues”
• Section A.12, “General Issues”
• Section A.13, “Testing Issues on SUT”
• Section A.14, “PXE Install Issues”
• Section A.15, “Time Test Issues”
• Section A.16, “KVM issues”
• Section A.17, “Kdump issues”
• Section A.18, “Product Entry and Reporting Information Entry issues”
• Section A.19, “PCI Pass-Through Issues”
• Section A.20, “IPv6 Information”
A.1 Installation Issues
A.1.1 Removing the ELIO Boot Tables

When a system is UEFI enabled, ELIO becomes the boot mechanism for SLES. Changing to the grub boot method
may not be easy. The following instructions are intended to remove the ELIO boot information and allow for grub to
be used on the hard disk drive.
Method 1: These instructions will delete any partition including the GPT .
1 Boot the system with a SLES or SLED (latest SP) DVD.
136 Troubleshooting and Help

2 Choose Rescue System. )
3 Login as user Root. No password is needed.
4 Type: parted /dev/sdx (e. g. /dev/sda) <Enter>.
5 Type: mklabel msdos <Enter>.
6 Type: yes <Enter> at the prompt to destroy the disk label and loose all data on the disk.
7 Type: quit <Enter>.
8 Repeat steps 4-7 for each disk drive.
9 Reboot the system.
Method 2: These instructions will wipe GPT ELILO information from the front and the back of the hard disk drive.
1 Boot the system with a SLES 11 (latest SP) DVD.

2 Choose the rescue mode. )
3 Login as user Root. No password is needed.
4 Use fdisk to find out the disk size by typing fdisk -l /dev/sda <Enter>. Example: SUT:~ # fdisk -l /dev/sda
5 The following output will appear.
Disk /dev/sda: 500.1 GB, 500107862016 bytes

255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf39173e3
Device Boot Start End Blocks Id System

/dev/sda1 2048 4208639 2103296 82 Linux swap / Solaris
/dev/sda2 * 4208640 109064893 52428127 83 Linux
/dev/sda3 109064894 976773167 433854137 83 Linux
6 Get the size of the disk in bytes. This is the first line of fdisk output. In the example above it is 500107862016.
7 Divide the size of the disk by 512 bytes. 500107862016 / 512 = 976773168.
8 Use dd to write zeros to the front of the disk. I used count=100, count=1 would be sufficient.
Type dd if=/dev/zero of=/dev/sda bs=512 count=100 <Enter>.
9 Use dd to write zeros to the end of the disk as well (seek value is 976773168 - 100 = 976773068).
Type dd if=/dev/zero of=/dev/sda bs=512 count=100 seek=976773068 <Enter>.
10 All ELILO information is now removed from the hard disk drive. The hard disk drive is ready to have the OS
installed with GRUB as the default boot mechanism.

A.2 Installing SLES On TC
• Section A.2.1, “TC Connection”
• Section A.2.2, “Configuring IP Addresses Using YaST”
• Section A.2.3, “Installing the missing rpms”
• Section A.2.4, “Installing the Test Kit manually on The SLES Xen VM”
A.2.1 TC Connection
You can test the connection to tclink by starting the tclink with the debug argument ( tclink debug). Then you can
telnet from any system to that tclink (e.g., telnet 10.1.1.1 7078). If there is a live connection, the linux tclink should
display some information on the screen as a result of the telnet. On linux, tclink communicates via the 7078 port. On
Java, tclink communicates via port 7076 but doesn’t print anything.
A.2.2 Configuring IP Addresses without Yast

If you are having trouble using YaST to configure the IP addresses of your NICs, you may use the following
commands.
______________________________________________________________________________________________
Command Description
___________________________________________________________________________________________________
ip addr show dev eth0 Show the configuration of the first NIC (eth0)
ip addr del dev eth0 10.1.2.2 Remove an IP address from the first NIC (eth0)
ifconfig eth0 10.1.2.2 netmask 255.255.255.0 Change the IP address of the first NIC (eth0)
___________________________________________________________________________________________________
A.2.3 Installing The Missing rpm's

The installation tool will display a message listing the missing rpm's which are needed. The following instructions
should be used in conjunction to add these missing rpm's.
1 At the terminal prompt, type yast2 sw_single <Enter>.

2 Next to Filter click and select Search.n) 6 April 2007
3 In the search box, type <missing rpm name> <Enter>, and then click Search.
4 Check the <missing rpm name> package for installation.
5 Repeat steps 3-4 for each missing rpm.
6 Click Accept to accept the Software Settings.
7 If prompted for automatic changes due to package dependencies, click Continue.
8 If prompted, insert SLES CD's as instructed, then click OK.
9 Click No at the Install or remove more packages window.
10 Insert the SCK Test Kit CD and run the installation script again.

A.2.4 Installing The Test Kit Manually On The SLES Xen VM
1 On the host, log in as root.
2 Start all VM's.
3 Insert the current System Test Kit CD. The CD will mount automatically.
__________________________________________________
Note: The notification may open behind the shell screen.
__________________________________________________
4 If prompted, click Cancel to the “What do you want to do?” question in the CD-ROM Daemon prompt, or close the
CD contents display window.
5 Open a terminal on the associated host: SLES 11 SP4 (on SUT).

6 Type /<mount point>/sck_copy_install_files.sh <Enter>, Example: /media/CDROM/sck_copy_install_files.sh
<Enter>.
7 Enter the IP address of the Guest VM to install and press <Enter>.

8 Follow the on screen instructions.
9 Once the installation has completed, switch to the associated Guest Console: SLES 11 SP4 VM.
10 Open a Terminal.
11 Type /root/sck-kit/sck_install.sh <Enter>.
11 Choose the option “Guest VM system” <Enter>.
12 If prompted, enter the IP address of TestConsole (10.1.1.2).
13 Repeat steps 6-12 for each associated VM: SLES 11 SP4 VM.n) 6
April 2007
A.3 TestConsole
• Section A.3.1, “TestConsole displays Error Attempting to Run Test”
• Section A.3.2, “TestConsole has Blank Screen during Testing”
If you are having trouble running TestConsole, read these sections before contacting a support representative.
A.3.1 TestConsole displays Error Attempting to Run Test
If “Error attempting to run test” appears on the TestConsole log screen, check /var/opt/ suse/TestKits/ for log files.
If you deleted the icon on the desktop for TestConsole, you probably cannot get the icon to reappear on the desktop by
reinstalling the kit. The way to get the desktop icon back is to remove the /root/.skel/tc.icon file, log out
and log back into TestConsole.

A.3.2 TestConsole Locks Up or has Blank Screen during Testing
If TestConsole locks up or has a blank screen during testing, the following is advised:
1 TestConsole may be busy. Wait 10 minutes for the TestConsole window to be redrawn. We have seen this in our lab
environment.
2 Click on the TC Terminal window. Then click on the TestConsole window.

3 Check for message screens hidden behind other screens. A message screen may be hidden and be waiting to have
the OK button clicked on before the TestConsole screen will be displayed correctly.
A.4 Time Synchronization Issues

• Section A.4.1, “Checking the Time Synchronization Configuration”
• Section A.4.2, “Time Sync Test Fails or Time Sync Verify Test Fails”
A.4.1 Checking the Time Synchronization Configuration

Please note that SUT and TC both need to be synced to the same exact time. This also means that the Time Zone, and
UTC Time must be chosen to be the same on both systems.
1 Verify that TestConsole is functioning as a time server (NTP server).

1a On TC open a terminal and type /etc/init.d/ntp status<Enter>.
1b If the status does not state running then type /etc/init.d/ntp start <Enter>.
2 Verify that the SUT is using TestConsole as a time server.
2a Ensure that each system can ping each other (Example type: ping 10.1.1.1 <Enter>).
2b On SUT type yast2 ntp-client<Enter>.
2c Enter the IP address of TestConsole in the NTP Server field.
2d Click Finish.
2e Ensure that ntp is running. On SLES 11 type /etc/init.d/ntp restart<Enter>. The status should be “done”.
2f Wait 60 seconds, the system should synchronize its time with TestConsole. If the time does not synchronize
repeat all steps in 1 and 2.
A.4.2 Time Sync Test Fails or Time Sync Verify Test Fails
With the release of 7.7 Test Kit we have sometimes seen an issue with the time synchronization. Some symptoms of
this are the failure of the Time Sync Verify Test and the failure of the Time Sync Test. The correction is to add
missing information to the /etc/hosts file.

1 On both the the TC and the SUT open a terminal.
2 Type cat /etc/hosts <Enter>.
3 Check the information listed in the terminal for 2 important lines. The loopback line and the system information
line must be present. Examples are below.
TC Example:
127.0.0.1 localhost
10.1.1.2 TC.suse TC
The pattern is <TC IP address> <TC machine name.domain> <TC Alias name>.
SUT Example:
127.0.0.1 localhost
10.1.1.1 linux_vt1l.suse linux_vt1l
The pattern is <SUT IP address> <SUT machine name.domain> <SUT Alias name>.
4 If either of the lines are missing then add the missing line to the /etc/hosts file.
5 The terminal window can be closed.
6 Run the failed time test again.
A.5 Component Check Issues

If component check will not start, ensure the TC system can ping the SUT. If ping fails, check the LAN wiring, the IP
addresses, the masks and gateway addresses.
If the SUT information or any components (LAN, HBA, HDD, etc.) are not showing up in the Product and Report
Information Entry tabs, then run the component check again.
A.6 Validate Install Test, Component Check, and Get Test Logs
If the Install, Component Check, or Get Test Logs test doesn't finish, it is possible that the current project was not
initialized completely.
Solution:
1 On the TestConsole of TC, double-click the first IP address in the current project.
2 Backspace over at least one character of the IP address selection and reenter the IP address.
3 Click OK.
If the Install, Component Check, or Get Test Logs test doesn't finish, it is possible that the install did not complete
successfully.

Solution:
1 Reinstall the Test kit on the SUT (see 2.3.3 Installing the Test Kit on the SUT)
2 Verify the install has completed successfully before restarting the tests.
If the Install, Component Check, or Get Test Logs test doesn't finish, it is possible that the IP address of the SUT was
not entered, or entered incorrectly.
Solution:
1 Reenter the SUT's IP address in TestConole's current project on the TC (see 2.8 IP Address Information).
2 Restarting TestConsole may be necessary if the test is hung and won't finish. Worst case, both the TC and SUT may
have to be rebooted.
A.7 Get Test Logs Test

• Section A.7.1, “Test logs location”
• Section A.7.2, “Failure to gather the test logs”
A.7.1 Test Logs Location

The test log files are located on the SUT and on the TC at or below the following path:
/var/opt/suse/testKits/system/<project name on TestConsole>
Look for .log files in and below this directory for the various tests. These log files will not be deleted from the TC or
SUT systems. It is advisable to manually delete the test directories when hard disk drive space is needed.
A.7.2 Failure to Gather the Test Logs

If the test log files are not being gathered as the problem could be a broken mount point. Below are tips to repair the
broken mount point. If the "Get Test Logs" test does not work, then ensure that the TestConsole is not running
remotely. The "Get Test Logs" test will not work remotely. You must be sitting in front of TC (Not remotely and Not
by SSH) to be using the TC system during testing.
If the "Get Test Logs" test fails, then check to see if the mount point exists.
1 Open a Terminal on TC.
2 Type ls /mnt/<IP address of SUT> <Enter>.
3 If the root directory of SUT does not get listed, then this is the cause of the failure. The nfs mount point is missing
from TC or not working correctly. To re-establish the mount point do the following:
3a Open a Terminal on TC.

3b Type umount -l /mnt/<IP address of SUT> <Enter>.
3c Type mkdir -p /mnt/<IP address of SUT> <Enter>
3d Type mount -t nfs <IP address of SUT>:/ /mnt/<IP address of SUT> <Enter>.
___________________________________________________________________

Note: If you have a bad mount point, do not use the df instruction.
___________________________________________________________________
OR
Reboot the the systems (SUT, TC) and restart Tclink.

On the physical SUT (Not Remotely or by SSH) do the following:
1 login as root
2 Open a terminal.
3 Type the following command: rctclinkd restart & <Enter>.
On TC start the test again.
A.8 Video and Desktop Effects Testing Issues
A.8.1 Video Test Issues

If video does not work properly, type yast2 <Enter> at a shell prompt and change graphic settings as needed. This
change will need to be in a config note.
A.9 Serial Port Test

• Section A.9.1, “Serial Port Test Fails”
• Section A.9.2, “Checking the Serial Port functionality”
• Section A.9.3, “Serial Port debugging with Minicom”
A.9.1 Serial Port Test Fails

If you experience a failure with the serial port test, it may be that the mgetty process is hung or not responding or the
pppd may not be responding. This is an issue which occurs on TC and on SUT. There are a number of corrections to
try.
Correction attempt 1:
Do the following on SUT:

1 Login as root.
2 Open a terminal.
3 Check to see if pppd is stuck by typing: ps aux | grep pppd | grep -v grep <Enter>. If pppd is listed then it is stuck.
4 Kill the stuck pppd process by typing the following command: killall -9 pppd <Enter>.
Do the following on TC:

5 Login as root.

6 Open a terminal.
7 Check to see if mgetty is listed by typing: ps aux | grep mgetty | grep -v grep <Enter>.
8 If mgetty is listed then restart the mgetty process by typing the following command: killall -9 mgetty <Enter>.
9 Run the serial port test again as described in the testing section of this documentation.
Correction attempt 2:
1 Reboot the SUT
2 Once the SUT is shutdown and rebooting, then reboot TC.
3 Once the SUT and TC are up and running, login to each as root.
4 Run the serial port test again as described in the testing section of this documentation.
A.9.2 Checking the Serial Port functionality

Performing the steps below will help determine if the serial port is functioning correctly. These steps should be
performed after section A.9.1 and before starting the serial port test again.
1 Open a terminal on SUT.

2 Type pppd ttyS0 115200 <Enter>.
There will be a series of onscreen messages. If there is a failure message then the serial port is either not configured
correctly or not functioning correctly. The next page displays a normal functional serial port message screenshot.
3 Press <Ctrl-c> to kill this process.

A.9.3 Serial Port Debugging with Minicom
If you experience difficulties with the Serial Port Test, do the following to determine if the serial port works. Your
internal company engineers, who know the hardware, can provide the necessary information to configure the serial
port.
1 Ensure that the serial port cable is connected between TC and SUT. SUT and TC Com port 1 must = 3f8 IRQ4. The
speed used during testing is 115,200.
2 (On TC) Use Minicom Terminal Emulator to receive output.

2a At the shell prompt, type the following: minicom -s <Enter>.
2b Select Serial And Port Settings
____________________________________________________________________
Note: The speed of the com 1 port on TC and SUT must be the same.
____________________________________________________________________

2c Ensure that the serial port setting is: /dev/ttyS0
________________________________________________________________________________
TIP: Pressing <Ctrl+A> release then press O, displays the Minicom configuration screen.
________________________________________________________________________________
2d After the port was configured save the settings, then exit the menu.
(en) 6 April 2007
3 (On SUT) Send output to TC via the serial port.
3a At the shell prompt, type echo -e “The serial port is working” > /dev/ttyS0 <Enter>.
OR
At the shell prompt, type cat /etc/hosts > /dev/ttyS0<Enter>. This outputs the contents of the file hosts to the
serial port. This information sent to the serial port on SUT should appear in the minicom screen on TC.
Minicom may display one character per line or display a complete sentence per line.
4 (On TC) Exit minicom. In the minicom window, press x, then select Yes.
A.10 Stress Tests

• Section A.10.1, “NIC issues”
A.10.1 NIC Issues

If, when re-configuring the IP address of either of the two NICs, YaST consistently reboots after you click the Finish
button at the Save Configuration Files window, the only way to edit the IP addresses of the NICs in the system is to
edit the files that start with the following: /etc/sysconfig/network/ifcfg-eth
There will be a file for each NIC which include the IP address and mask of the NIC.
To enable IP forwarding when YaST2 does not allow you to save the configuration:
1 Edit the contents of the following file to be “1” instead of “0”:
/proc/sys/net/ipv4/ip_forward
This will enable IP forwarding value will reset to the original value when the system reboots.
2 To make the configuration persistent, edit the /etc/sysconfig/sysctl file with the line that has “IP_FORWARD” to
read IP_FORWARD=’yes’
If the steps above don’t work, try the following.
1 At a terminal, type ls /srv/ftp/ and verify the following files are listed: 300kb.md5sum, 300kb, 400mb,
400mb.md5sum
If your LAN connection is having issues, see the checklist below.
1 How are you determining that the NIC speed is correct?
2 Is the certification testing in a secluded network?

3 How many computer systems are on the certification testing network? There should only be 2.
4 What speed of the switch/s in the certification testing network?
5 The Ethernet cables must support the highest speed NICs in the SUT. What is the speed of ethernet cables being
used between TC and SUT?
6 What is the IP address of:

6a SUT?
6b TC?
7 What is the OS installed on:

7a TC?
7b SUT?
8 AppArmor should not be installed on the TC with SLES 11. Is AppArmor installed on TC?
If the NIC test fails, it could be because the old Test Kit was not uninstalled completely on the TC and SUT machines.
1 Remove old files on TestConsole:
1a Open a terminal on TestConsole.
1b Type rm -rf /srv/ftp/*<Enter>.
1c Type run configure_tc<Enter>.
A.11 Test Kit Installation Issues

• Section A.11.1, “Yast requests a change of CD/DVD or unable to change CD/DVD”
If during install, YAST asks you to change the CD/DVD to the SLE installation disk:
1 Abort out of YAST.
2 Type <CTR+C> to kill sck_install.sh
3 Copy the contents of the System Certification Kit (SCK) CD to /root/Desktop/SCK
4 Eject the SCK CD
5 Run /root/Desktop/SCK/sck_install.sh
or
1 Note what package it is trying to install.

2 Abort out of YAST.
3 Type <CTR+C> to kill sck_install.sh.
4 Enter "cd /" to change out of the SCK install directory so the CD can be ejected.
5 Enter "eject" to eject the System Certification Kit (SCK) CD.
6 Run yast2 and install the missing package.

7 Eject the SLE installation disk and put the SCK CD in the drive.
8 Re-run sck_install.sh
9 Repeat if necessary.
A.12 General Issues

• Section A.12.1, “Hang after reboot”
• Section A.12.2, “Test Run More Than 12 Hours”
• Section A.12.3, “USB Tests Fail”
A.12.1 System Hang After Reboot

If the SUT hangs after reboot, the problem may be that the USB hard drive cannot be mounted. Follow the steps
below to remove the USB Hard drives from the SLES configuration and recover. The /etc/fstab file can be
edited after a reboot with the USB drives attached.
1 Log in as root.
2 Open a terminal and type vi /etc/fstab<Enter>.
3 Place the cursor on the line with the USB entries (i.e., /media/tc/usb1 or /media/tc/usb2) and press D
two times in a row. This will delete the line.
4 Unplug the USB hard drives from the system (if you have not already done so).
5 Reboot the system. The USB hard drives will not be configured with the system.
A.12.2 Tests Run More Than 12 Hours

Possible Problem 1:
The Testconole has been run twice. There are 2 instances of TestConsole running on the TC.
Possible solution 1:
Close all instances of TC. Then open TestConsole and the project then start from where you left off.
Possible Problem 2:
The system clock is running slow:

1 Look at the clock display on the main screen and verify it is the same time as the Test Console machine.
2 If it is close or the same time, go on the the next possible problem. Otherwise go on to the next step.
3 You have a hardware/OS incompatibility. You can try the possible solution, but you must fix the problem or
document a workaround for your customers.

Remove apci and/or acpi functionality from your machine:
1 Edit /boot/grub/menu.lst
2 At the end of each line that starts with "module", append the following:
apci=off, acpi=off
3 Save the file and reboot the machine.

4 Run the tests again and verify the symptoms have disappeared.
Possible Problem 3:
Hardware/OS incompatibility - The test process is hung, indefinitely waiting for an I/O or an event to complete.
Check the process state to see if the test process is hung:

1 Open a terminal
2 Determine what the test process name from the test being run.
Test Test Process Names Location
------------------------------------------------------------------------------------------------------------------------
Floppy badblocks, dd, or mke2fs SUT
Serial wget, md5sum, or sync SUT
CD/DVD cmpdir, dd, cmp, or ls SUT
CDW cmpdir, or cdrecord SUT
DVDW cmpdir, or cdrecord SUT
USB bonnie SUT
Hard Disk bonnie SUT
Raid bonnie SUT
CPU/Memory eatmem SUT
NIC md5sum, wget, or sync SUT
Router md5sum, wget, or sync TC
3 Run the following command: "top"

4 Look for any of the Test Process Names of the test that is still running.
5 If the test process name shows up in top's list, go on to the next possible problem. Otherwise go on to the next step.
6 Repeat the following step for each test process name:
6a Run the following command: "ps aux | grep -f <Test_Process_Name>"
6b Look at the process state code. If it is consistently one of the following codes you probably have a hung process.
PROCESS STATE CODES:
D Uninterruptible sleep (usually IO)
S Interruptible sleep (waiting for an event to complete)
1 Get an Engineer involved and try to find out why the process is hung and fix the problem.
2 Then either kill the process (with -9) or reboot the machine.
3 Run the tests again and verify the incompatibility has been fixed.
Possible Problem 4:

The tests have been run twice.
1 Verify that the process is not hung (see above). If it is not, cancel all the tests making sure they have all finished
before starting over.
2 Run the test group "Stress Tests" to avoid starting a test twice.
A.12.3 USB Tests Fail

If the USB test fails, try the following steps.
1 Log into SUT as root.

2 Open a terminal and type the following: hwinfo - -disk <Enter>.
3 Write down each USB disk device “Device File” information in order from top to bottom. Each disk section will
have information such as:
Vendor: usb ...

Device: usb …
.
.
.
Device File: /dev/xxx (example: /dev/sda)
4 Notice the order of the USB devices. The first USB device listed will be USB disk 1 and will correspond to the
USB 1 Test. The second USB device listed will be USB disk 2 and will correspond to the USB 2 Test.
5 If a disk device has a line which states has a “Drive status: no medium” then some type of memory or disk must be
put into the device in order for the test to pass.
A.12.4 Multiple Test Projects on TC

Test console does not support multiple projects during testing. For questions about this please contact your SUSE
Support Engineer.

A.13 Testing issues on SUT
• Section A.13.1, “Tests will not start”
A.13.1 Tests will not start on SUT
Solution A:
When the tests will not begin to run on TC, this may be due to a connection problem from TC to SUT.
To check the connection ping from TC to SUT. Then ping from SUT to TC. If ping fails, check all cables and
switches. Ensure that the NIC cards are properly configured on TC, and SUT.
Solution B
The problem may be that Tclink is not running, or not running properly on SUT. Do the following:
1 Open a terminal on SUT.

2 Type the following command: rctclinkd restart & <Enter>.
3 On TC start the test again.
A.14 PXE Install Issues

Problem: The SUT has been booted with PXE and cannot see the OS images on TC to begin the OS install.
Possible cause: The ip address of the TC was changed after the TC was set up as a PXE install server.
Solution: On the TC, use the config install server utility (configinstserver.sh) to remove all ISO images. Then use
the config install server utility (configinstserver.sh) to add the ISO images. The images should now be available to
the SUT for PXE boot installation. See Section 2.2.3, “Setting up the DHCP/PXE server on TC” for details about the
config install server utility (configinstserver.sh).
A.15 KVM Issues

• Section A.15.1, “KVM Not Responding”
• Section A.15.2, “KVM Time issues”
• Section A.15.3, “KVM Guest Time is not in sync with host”
A.15.1 KVM GUI Not Responding

This section addresses some problems and solutions for the KVM not responding.
Symptom: KVM GUI is non-responsive. The Virt Manager sometimes gets confused causing the guests to look like
they are hung.

Possible Solution: Close all Guest windows and restart the Virt Manager. Then open each Guest window.
Possible Solution: The systems does not have the minimum memory requirements or the KVM guests don't have the
minimum memory requirements assigned. See the KVM section for memory requirements.
A.15.2 KVM Time issues

This section addresses the time being different on a KVM guest compared to on the KVM host.
Symptom: the time on the KVM Guest will not stay in sync with the KVM host.
The following parameters can be used to help the problem. The steps below are only effective when used during
booting of the OS.
1 Restart the KVM guest
2 When the boot menu appears, press the down arrow once then press the up arrow once. This will place the selection
back to the default OS boot.
3 This will place the cursor back on the top default boot selection and stop the boot.
4 Add the following to the boot options line:
For SLES 11 SP4 type <space>no-kvmclock <Enter>.
5 The KVM Guest system will boot. In order to use the no-kvmclock setting it must be entered on the boot line each
time the system is booted.
A.15.3 KVM GUEST Time is not in sync with Host

This section addresses problems which have occurred with the KVM Guest loosing time. We have seen the problem
with KVM guests loosing time and being out of sync with the KVM Host. Below are boot parameters which can be
used to attempt to correct this problem. Try using both parameters during the KVM guest boot.
1 notsc
2 divider=10
A.16 Xen Issues

• Section A.16.1, “Xen Guest Time is not in sync with Host”
A.16.1 Xen GUEST Time is not in sync with Host

This section addresses problems which have occurred with the Xen Guest loosing time. We have seen the problem
with Xen guests loosing time and being out of sync with the Xen Host. Below are boot parameters which can be used
to attempt to correct this problem. Only use one of the parameters at a time.

1 notsc
2 divider=10
3 independent_wallclock=1
Here are steps to try which may correct the with the sporadic clock, without rebooting the system:
1 From a root prompt on the VM, type the command: echo 1 > /proc/sys/xen/independent_wallclock
2 changing the /etc/sysctl.conf configuration file and adding:
# Set independent wall clock time

xen.independent_wallclock=1
3 Run the tests again. Watch to see if the clock stays in sync.
A.17 Kdump Issues

• Section A.17.1, “Changing the Kdump Settings”
• Section A.17.2, “Manually Starting the Kdump”
• Section A.17.3, “IP address issues with kdump”
A.17.1 Changing the Kdump Settings

If the kdump test is not functioning, then change the kdump settings on the SUT using the following instructions.
On the SUT:
1 Open a terminal.
2 Open the kdump setting by typing yast2 kdump<enter>.
2a If kdump is not enabled then click on enable kdump.
3 Select the Dump filtering.
4 Unselect/uncheck the following:
4a Pages filled w/zero
4b Free pages
5 Select startup
5a Increase or decrease the memory amount. See the Crashkernel Memory Guidelines below for more information.
6 Click OK to save the changes.
7 Reboot the SUT.
8 Run the kdump test again.

Crashkernel Memory Guidelines
SLES 11 (latest SP)

On SLES 11 try increasing or decreasing the crashkernel amount.
Examples of increases:
crashkernel=512M-:64M or
crashkernel=512M-:256M
Examples of decreases:
crashkernel=64M-:32M
SLE 12 (latest SP)

The system should automatically adjust the high and low memory kdump parameters. If kdump does not function
then try increasing or decreasing the low or high memory amount. The low memory setting uses RAM below 4GB.
The high memory setting is intended for systems with more than 4GB of RAM.
Examples:
Low memory: 256
High memory: 128
A.17.2 Manually Starting the Kdump

For a sanity check the kdump can be manually run on the SUT. To manually run kdump do the following:
1 On the SUT open a terminal.

2 Type sync <Enter>.
3 Type echo c > /proc/sysrq-trigger <Enter>. The kdump process will begin.
A.17.3 IP Address Issues with Kdump

If the test harness (SUT and TC) are not on a secluded network or one of the LAN adapters is on a different network,
it is possible that the IP address configuration on TC is causing problems with the kdump test. This happens when
eth0 is configured for a different IP address then the testing network. The steps to change this on TC are as follows:
1 Open a Terminal on TC.

2 Type yast2 lan<Enter>.
3 Select the adapter.
4 Click edit.
5 Click on the hardware Tab.

6 Click change next to the device name.
7 Select, by check mark, to change the device name.
8 Type the name of the new adapter into the name field. If an eth0 adapter already exists, then it must first be changed
to something else (e.g. eth9).
9 Click OK.
10 Click next.
11 Click OK. the yast2 lan window will close.
12 Run the kdump test again.
A.18 Product and Report Information Entry Issues

Section A.18.1, “Product and Report Information - Missing Device”
A.18.1 Product and Report Information - Missing Device

There are instances when a device is missing from the product information, such as a LAN adapter. This can occur if
a device is added to the SUT after the component check test is run. If this occurs then ensure that the device is
installed and enabled, then run the component check again.
A.19 PCI Pass-Through Issues

Section A.19.1, “PCI Pass-Through – VM Fails to Start”
A.19.1 PCI Pass-Through – VM Fails to Start

Problem: VM fails to start after passing-through a NIC in KVM or XEN. The error is:
"Error starting domain: internal error: Unable to reset PCI device 0000:02:00.0: internal error: Active 0000:02:00.1
devices on bus with 0000:02:00.0, not doing bus reset"
Solution: The passed-through NIC card has ports 02:00.0 and 02:00.1 as shown below:
linux-y5w9:/home # lspci | grep Ethernet

...
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
Convert colon and dot to underlines to find the address in correct format:
linux-y5w9:/home # virsh nodedev-list | grep 02_00_0

pci_0000_02_00_0
Detach the passed-through NIC with command "virsh nodedev-detach ..." and detach each port:
linux-y5w9:/home # virsh nodedev-detach pci_0000_02_00_0

Device pci_0000_02_00_0 detached

linux-y5w9:/home # virsh nodedev-detach pci_0000_02_00_1
Device pci_0000_02_00_1 detached
Attempt to start VM again, it should start at this point.
A.20 IPv6 Information

Section A.20.1, “Ipv6 Address Generation”
A.20.1 IPv6 Address Generation

IPv6 address on TC:
The TC's IPv6 addresses are generated during the install of the Yes Certification Test Kit. If you change any IP address
on the TC, you must re-install the Yes Certification Test Kit.
IPv6 address on SUT:

The SUT's IPv6 addresses are generated during the NIC test.
Test Kit IPv6 address generation:

The address starts with fc00 or fd00, then the IPv4 network address is converted to hex and added after fc00 or fd00.
(example: 10.1.1.0 network becomes IPv6 address fc00:a1:100. Then the MAC address is added to the end (example:
00:0E:0C:64:DE:6C MAC becomes IPv6 address fc00:a1:100::e0c:64:de6c.
A.21 Hibernate Test Issues

Section A.21.1, “Hibernate Test PASS w/WARNING”
A.21.1 Hibernate Test PASS w/WARNING

If the Hibernate test result is PASS w/WARNING, it may be caused by a device in the SUT which did not recover
from the hibernate. In order to investigate the problem the log files will be needed. These log files can contain a large
content of information. The best way to discover the problem is to look through the time stamps which correlate to
the time of the hibernate test. These files may or may not exist and may or may not contain information about the
issue, it depends on the cause of the PASS w/WARNING. The log files are as follows:
/var/log/messages (This file can be overwritten and needs to be reviewed soon after the PASS w/WARNING)
/var/log/pm-suspend.log (If this file exists it will contain information about the last suspend and can be overwritten.
The file needs to be reviewed soon after the PASS w/WARNING)
/var/log/suspend2disk.log (If this file exists it will contain information about the last suspend and can be erased. The
file needs to be reviewed soon after the PASS w/WARNING)
/var/log/boot.msg (This file can be overwritten at boot and needs to be reviewed soon after the PASS w/WARNING)

A.22 Sleep Testing Issues
Section A.22.1, “Sleep Test PASS w/WARNING”
A.22.1 Sleep Test PASS w/WARNING

If the Sleep test result is PASS w/WARNING, it may be caused by a device in the SUT which did not recover from the
Sleep. In order to investigate the problem the log files will be needed. These log files can contain a large content of
information. The best way to discover the problem is to look through the time stamps which correlate to the time of
the Sleep test. These files may or may not exist and may or may not contain information about the issue, it depends
on the cause of the PASS w/WARNING. The log files are as follows:
/var/log/messages (This file can be overwritten and needs to be reviewed soon after the PASS w/WARNING)
/var/log/suspend2ram.log (If this file exists it will contain information about the last suspend and can be overwritten.
The file needs to be reviewed soon after the PASS w/WARNING)
/var/log/pm-suspend.log (If this file exists it will contain information about the last suspend and can be erased. The
file needs to be reviewed soon after the PASS w/WARNING)
/var/log/boot.msg (This file can be overwritten at boot and needs to be reviewed soon after the PASS w/WARNING)
A.23 USB Virtualization Pass Through Setup

To pass a USB drive through to a KVM or XEN guest the following instructions are provided. A physical USB
device may be passed from the VM Host Server to the VM Guest. Given the very wide variety of USB devices
available, it is anticipated that some devices may not work properly.
1 Plug the USB drive into the SUT.

2 On the Host type lsusb.
3 Write down the bus and device information.
4 Make sure that the SLES VM (Guest) is installed but not running.
5 In the virt manager for the SLES VM (Guest) click on the info button along the top of the screen.
6 Click on USB Controller.
7 On the right side of the screen, click USB Type drop down. Choose Default for USB 1.1 or USB 2 for a USB 2.0,
or choose a USB 3 for a USB 3.0 device. Make sure to choose the USB version which matches the USB port
which will be used.
8 Click on add hardware.
9 Choose the USB Host device.
10 Click on the device detected in step 2.
11 Click on Finish.
12 The USB device will mount and be displayed in the VM (Guest) GUI.

B
Uninstalling the Test Kit from a Linux System
Automatic Uninstall
1 Log in to the system as root.
2 Open a terminal or shell.
3 At the shell prompt, type sck_uninstall.sh
4 Answer Yes all on screen questions to complete the uninstall.
5 All remaining files will also need to be installed by doing the following:
5a At the shell prompt, type rm -r /var/opt/suse/TestKits
5b At the shell prompt, type rm -r /opt/suse/TestKits
OR Manual Uninstall
The Test Kit may also be uninstalled from TC by typing the following commands at a shell prompt.
1 Type rpm -e sck-tc <Enter>.
2 Type rpm -e tconsole <Enter>.
3 Type rpm -e tclink <Enter>.
4 Type rpm -e sck-common <Enter>.
The Test Kit may also be uninstalled from SUT by typing the following commands at a shell prompt.
1 Type rpm -e sck-sut <Enter>.
2 Type rpm -e tclink <Enter>.
3 Type rpm -e sck-common <Enter>.
If you would like to verify that the kit was uninstalled, type the following commands at a shell prompt:
158 Uninstalling the Test Kit from a Linux System

1 Type rpm -q tconsole <Enter>.
2 Type rpm -q tclink <Enter>.
3 Type rpm -q sck-common <Enter>.
159
C
Using TestConsole
This section covers the following topics:
• Section C.1, “Introduction”
• Section C.2, “Project Contents”
• Section C.3, “Run Queue”
• Section C.4, “Project Log”
• Section C.5, “TestConsole Testing Modes”
• Section C.6, “Importing Product Information from an Existing Project”
• Section C.7, “TestConsole Error Messages”
C.1 Introduction
The TestConsole main window displays three distinct panes: Project Contents, Run Queue, and Project Log. You may
display these panes in tiled or tabbed formats. You can change the display in the View menu. We recommend the
tabbed view if your monitor has a lower than 1024x768 resolution. Each open test project is displayed on its own tab
and can be quickly accessed by clicking on the tab with the test project name.
C.2 Project Contents

The Project Contents pane uses an expanding tree format to display the tests associated with the project you have
chosen. For example, to expand or collapse a group of tests, click the plus or minus icons next to the test. There are
three columns in the Project Contents pane. The first column displays the title of the test. The second column indicates
whether the test is selected to be run with a test group (blank box = unselected, check mark in box = selected). The
third column indicates the final test result (untested, pass, fail, etc.). The Project Contents pane may also display a
Station Address icon (computer icon) to enable you to select your test station.
C.2.1 Starting Tests

1 Double-click any item in the Project Contents pane and the test will start.
2 Right-click any item in the Project Contents pane and choose an item from the popup menu to view its properties.
3 TestConsole saves project files once a test has stopped. This includes product information and test results.
C.2.2 Selecting and De-selecting Tests

To select or de-select a test, click the boxes in the second column. A check mark in the column indicates you have
selected the test.
n) 6 April 2007
160 Using TestConsole

C.3 Run Queue
The Run Queue pane displays the tests that are currently running or queued to start. It displays the test name, the
status and the IP address of the test station. The Cancel Test button enables you to cancel the highlighted test that is in
the Run Queue. The Cancel All button cancels all tests that are queued to run. The Remove Test button allows you to
remove a test, even if it is hung.
______________________________________________________________________________________________
Note: When a test is running, the word “running” appears in the status column. If the station under test loses its
connection the status column will show two computers disconnected.
______________________________________________________________________________________________
C.4 Project Log

The Project Log pane displays a running log of the tests in your test project. It records the time each test started and
finished, the result of the test, and other pertinent information. To display additional information about the test, errors,
warnings, and failures in the Project Log pane, run the test in debug mode.
C.5 TestConsole Testing Modes

TestConsole can be run in additional testing modes which are not typically used during the certification testing. This
section (C.5) will provide information for the different modes.
C.5.1 Debug Mode

Debug Mode displays additional information about errors and failures encountered while running the test. This
information is displayed in the Event Log pane of the TestConsole window. Not all test modules support the logging
of debug information. To enable debug mode, click the Debug check box in the Event Log control bar. Debug mode
runs slower than the normal test mode and can quickly fill up the event log. By default, the log is limited to 10,000
entries. When it exceeds 10,000, the entries at the beginning of the log are lost.
C.5.2 Loop Mode

Loop mode allows you to set up a list of tests or test groups in any order and to run the tests for a multiple number of
times in a loop. You can specify loop counts for individual tests as well as groups of tests.
Editing the Loop Test List
1 To create or edit the Loop Test List, from the menu bar select Loop > Edit Loop List. This will display a dialog box
with two panels. The left panel displays the available Project Contents. The right panel displays the Loop Test List.
2 In the Project Contents panel, select the test or group that you want to add to the Loop Test List and click Add. The
selected items will be added to the loop list. You can continue to add items in any order.
en) 6 April 2007
3 To delete a test or group, select the item in the Loop Test List panel and click Remove.
4 To rearrange the order of the tests within a group, right-click the item in the Loop Test List panel and select Move
Up or Move Down from the popup menu.
5 To edit the loop count for individual tests or test groups, either double-click the Loop Count column next to the test
title or right-click the test title and select Loop Count. This displays a dialog that allows you to edit the loop count
properties. The Loop Test List will be saved until the project is closed. You can close the Loop dialog at any time.
Starting the Loop Test List

1 If the Loop List dialog window is open, click Run List.
2 If the Loop List dialog window is closed, from the menu bar click Loop> Run Loop List.

____________________________________________________________________________________________
Note: Currently, loop mode restricts the number of test instances that can be placed on the Run Queue to 100
maximum. For example, if you have 2 tests in a group that run 25 times each with the group itself running 2 times,
then you have reached your maximum.
____________________________________________________________________________________________
Choose tests to run

1 Choose the test to be enabled.
2 Double-click Enable . . . Testing to enable the test.
C.6 Importing Product Information from an Existing Project

You may import product information from an old project into a new project. TestConsole will only import the product
information. TestConsole will not import test results. Importing product information will delete all test results of the
current project. Import product information before you perform any tests.
1 Start TestConsole.
1a Bring up the TC workstation.
1b Double-click the TestConsole icon on the desktop.
2 Open the Project.
2a Click Project > Open Test Project > New.
2b Select (Server or Client) - Full or (Server or Client) - Reduced and click Select.
2c Click Yes at the Warning! window to enter the SUT product information now.
3 Import the project.
3a Click File > Import Product File.
3b Click Yes at the Warning! Window.
3c Browse for the project file to be imported in the /opt/suse/testKits/System/status
directory (e.g., YourFile.TSF).
3d Remove all drivers and adapters listed in the video, LAN, and HBA tabs.
3e Click OK in the Product & Report Information window.
4 Save the project.
4a Click Project > Save Test Project As.
4b Replace the project name with a unique name (e.g., P2System).
4c Click Save.
____________________________________________________________________________________
Note: TestConsole will import all of the product information into the current project, and it will
reset all test results. Remember to change all pertinent information before starting any tests.
____________________________________________________________________________________
4d Make any necessary changes in the product information.

4e Click OK.

C.7 TestConsole Error Messages
Error messages will occur for a variety of reasons (e.g., incomplete required information or test results). Error
messages indicate problems with required tests or product information. All required tests must be completed or have a
valid exception approved by SUSE in order to receive a bulletin. TestConsole will produce an error message for each
required test that does not pass or have test results. These tests must be completed (or have a valid exception) in order
to receive a bulletin. TestConsole will also generate an error message for each required empty field in the Product and
Reporting Information screen forms. Each required field must be completely filled in to receive a bulletin.
______________________________________________________________________________________________
WARNING: Any changes to fields in the System tab (except the Product Description field) will reset all test results
for the product. Contact a SUSE Engineer if changes must be made to these fields.
______________________________________________________________________________________________
C.7.1 TestConsole Warning Messages

Warning messages also occur for a variety of reasons (e.g., incomplete optional information or test results).
TestConsole will generate a warning message for each optional test that does not have test results.
en) 6 April 2007

D
Adding Drivers to the SUT
D.1 Introduction
Below are some points regarding system Yes certification testing when drivers are added:
1 Downloaded drivers are permitted for usage during Yes Certification testing. Drivers which are downloaded then
installed onto the SUT for use during Yes Certification testing must have a config note on the bulletin.
Also, we have a process to provide supported drivers for use during Yes Certification testing. The process is called
the SUSE SolidDriver Program. See below for information about the SUSE SolidDriver Program. Only Drivers
from the SUSE SolidDriver Program will be supported by SUSE. Drivers from other sources are permitted for use
during Yes Certification testing but will not be supported by SUSE.
2 Recompiling the kernel to add a driver is not permitted for Yes Certification testing.
3 The driver URL location for downloaded driver must be provided in a config note on the bulletin. This allows
re-creation of the tested environment.
4 SUSE SolidDriver Program

SUSE builds drivers for partners through the SUSE SolidDriver Program. These drivers are typically accompanied
by a support agreement. Also these drivers do not have a tainted kernel issue. Prior to installing a driver please
search the SUSE SolidDriver Program area for the driver. The driver download location is:
http://drivers.suse.com/driver-process/pub/update/
and here:
http://drivers.suse.com/
More information is available about the SUSE SolidDriver Program from the following Link:
http://drivers.suse.com/doc/SolidDriver/
For additional SLES 11 SP4 driver support please refer to the SLES 11 SP4 release notes.
164 Adding Drivers to the SUT

D.2 Using kISOs
In addition to updated drivers, occasionally specific hardware will require an updated installation (initial boot) kernel
to fix a specific problem. SUSE uses “kISOs” (kernel ISOs) to provide updated installation kernels for specific
problems. kISOs are provided through the Partner Linux Driver Program and therefore they are considered supported.
When kISOs are used for YES Certification testing, a config note is required on the bulletin. The config note must
include an explanation of what problem was solved by using the kISO and the kISO URL. The kISO URL is needed
to enable a user to reproduce the tested configuration.
______________________________________________________________________________________________
Note: kISOs are created on a per-system basis for partners with SUSE SolidDriver Program-level Developer Services
contracts. For more information about the kISOs please see:
http://wiki.novell.com/index.php/PLDP:_PLDP_Concepts
______________________________________________________________________________________________
Installing using a kISO is done by booting from the kISO disk (or image) then swapping to the stock SLE media as
instructed by the install prompts. Although the system Test Kit does not include automated support for kISOs, the
Test Console PXE configuration files can be manually edited to support kISO installs. Use the following steps to add
a kISO to the list of SLE versions available through the Test Console PXE interface:
Configuring the SCK PXE Environment for kISO Installs
Prerequisites:
1 SCK should be installed on the TC system.

2 kISO should exist in a directory (e.g., /work/isos) on the TC system.
3 SCK PXE environment should already be configured to support a stock install of the SLE version supported by the
kISO.
On the TC:
1 Create a mount point for the kISO. Example: mkdir /home/InstSource/samplesystem-sle11sp4-kiso
2 Modify /etc/fstab to add an entry to mount the kISO. Example:

/work/isos/samplesystem-sle11sp4-kiso.iso /home/InstSource/samplesystem-sle11sp4-kiso \ iso9660 ro,loop
3 Mount the kISO. Example: mount /home/InstSource/samplesystem-sle11sp4-kiso
4 Add the kISO kernel and initrd files into the PXE environment. Example:
cp /home/InstSource/samplesystem-sle11sp4-kiso/boot/x86_64/loader/linux \
/tftpboot/kernels/samplesystem-sle11sp4-kiso-kernel
cp /home/InstSource/samplesystem-sle11sp4-kiso/boot/x86_64/loader/initrd \
/tftpboot/initrds/samplesystem-sle11sp4-kiso-initrd
5 Modify /etc/exports to add an entry to share the kISO mount point. Example:
/home/InstSource/samplesystem-sle11sp4-kiso *(ro,no_root_squash,no_subtree_check)

6 Export the kISO: exportfs -a
7 Edit the SCK PXE configuration file /tftpboot/pxelinux.cfg/default to add an entry for the kISO install.
7a Find the section with the header “# START Reserved for Partner OS Installs”
7b Add kISO single-disk, multiple-disk, and manual install entries:
Label samplesystem-sle11sp4-kiso-single-disk
MENU LABEL Samplesystem SLE11SP4 kISO - single disk install
kernel kernels/samplesystem-sle11sp4-kiso-kernel
append initrd=initrds/samplesystem-sle11sp4-kiso-initrd ramdisk_size=65536
install=nfs://10.1.1.2:/home/InstSource/SLES-11-SP4-DVD-x86_64-GM-DVD1 vga=791
showopts autoyast=nfs://10.1.1.2:/opt/suse/testKits/system/autoyast/SLES11_SP4-x86_64-
single_disk.xml addon=nfs://10.1.1.2:/home/InstSource/samplesystem-sle11sp4-kiso
Label samplesystem-sle11sp4-kiso-multiple-disk
MENU LABEL Samplesystem SLE11SP4 kISO - multiple disk install
append initrd=initrds/samplesystem-sle11sp4-kiso-initrd ramdisk_size=65536
install=nfs://10.1.1.2:/home/InstSource/SLES-11-SP4-DVD-x86_64-GM-DVD1
autoyast=nfs://10.1.1.2:/opt/suse/testKits/system/autoyast/SLES11_SP4-x86_64-
multiple_disks.xml splash=0 vga=791 showopts
addon=nfs://10.1.1.2:/home/InstSource/samplesystem-sle11sp4-kiso
Label samplesystem-sle11sp4-kiso-manual
MENU LABEL Samplesystem SLE11SP4 kISO - manual install
append initrd=initrds/samplesystem-sle11sp4-initrd ramdisk_size=65536
install=nfs://10.1.1.2:/home/InstSource/SLES-11-SP4-DVD-x86_64-GM-DVD1 splash=0
vga=791 showopts addon=nfs://10.1.1.2:/home/InstSource/samplesystem-sle11sp4-kiso

E
Identifying Vendor Device Ids
The Linux PCI ID Repository (http://pciids.sourceforge.net/) can help you identify various vendor and device IDs.
167 Identifying Vendor Device Ids

F
SBS Users Guide
F.1 Creating a Bulletin in SBS using a Bulletin Submission File
1. Open a web browser the SUSE Bulletin System. The URL is:
https://www.suse.com/nbswebapp/yesCert.jsp
2. Read the bulletin submission file (.zip) into SBS.
2.1. Click New Submission and browse to your bulletin submission file (.zip).
2.2. Click Upload.
3. The bulletin is now in the SBS system. Read through the Overview of the Bulletin States section below.
Afterward go to section F.2 for the instructions to move the bulletin from Open State to Review for processing.
Overview of the bulletin States

The following are the different states that a bulletin will go through. An email will be sent to the responsible parties
when a bulletin submission is moved to the Needs Response state or to the Final Customer Review state.
Open (Partner responsibility)

The bulletin submission has been read into SBS. The partner is able to view the submission and modify the
Product Description, some non-critical parts of the Tested Configuration, and Company Information. The
partner explains any issues that came up during testing. The partner then submits the bulletin submission to
the Review State.
Review (SUSE responsibility)

The Developer Services Engineer reviews the submission, and may edit any portion of the bulletin or request
additional information from the partner. The Developer Services Engineer then submits the bulletin
submission to a Needs Response state or a Final Review state.
Needs Response (Partner responsibility)

The Developer Services Engineer has questions or has found problems with the submission which need to be
resolved. The submission has been sent back to the partner for feedback. The partner provides the requested
information or corrects the problem then submits the bulletin submission back to a Review state.
Final Review (SUSE responsibility)

The Bulletin Reviewer must now review the summary for adherence to bulletin standards and make
corrections as needed. The bulletin Reviewer approves then submits the bulletin submission back to the
Review state (if more clarification is needed) or to the Final Customer Review state.
Final Customer Review (Partner responsibility)

The bulletin submission has passed all phases of the certification process. This state allows partners to
review the submission for any changes that SUSE may have made (the partner cannot change any information
on a submission in this state). This state also exists to allow partners to control bulletin release. The partner
then releases the bulletin. We will not revoke a bulletin once it is released.
168 SBS Users Guide

Release Pending (SUSE Responsibility - automated)
This is a temporary state that will last only a few minutes after the bulletin submission has been submitted for
release.
Released (SUSE Responsibility – automated)

The bulletin submission has been made into an official SUSE Yes Certification bulletin. The SUSE Yes
Certification bulletin is on the public web server. The public web server will still need an hour for the new
SUSE Yes Certification bulletin to appear on the search engine. The SUSE Yes Certification bulletin will be
available to public view at the Yes Certified Bulletin Search located at:
https://www.suse.com/yessearch/Search.jsp .
169 SBS Users Guide

F.2 Open State - Partner should do the following:
Do not open multiple bulletin screens in SBS at the same time. Doing so may cause bulletin changes to be unsaved or
inaccurate.
2. If you have not already done so, read the bulletin submission file (.zip) into SBS.
2.1. Click New Submission and browse for the bulletin submission file (.zip).
2.2. Click Upload.
3. Verify the product name is correct at the top of the summary. To edit the product name, click on the word "Edit"
(green font and underlined) to the left and above the SUSE Yes Certified Logo. Delete the existing product name
in Primary Product field. Type the new product name into the Primary Product field. Click submit at the bottom
of the screen.
4. Verify that the Product Description is correct. To edit the Product Description, click on the word "Edit" (green
font and underlined) above the Product Description. Type the new product description into the Product
Description field. Click Submit at the bottom of the screen. Follow these requirements:
4.1. Do not compare this product with any competitors. Words like “best” and “faster” are not acceptable.
4.2. Do not indicate that this bulletin applies in any way to other similar systems or products. All items in the
product description must have been present in the system during testing or in another certified system.
Do not list a “series” (i.e. 5500 series) to the product description.
5. Verify the Tested Configuration:

• Ensure that all component information (BIOS, Bus, CPU, HBA, etc) is complete and correct.
• For instructions to propose a new component see the section entitled “Proposing a Component in
SBS” in this document.
• Ensure that the interface and quantity exists and is accurate.
• To add the interface, click on the word "Edit" (green font and underlined) above tested
configuration. Scroll down to the device (host bus adapter, hard disk drive, CD/DVD device)
which needs the interface added . There is a field entitled "Interface" under the Quantity field.
• Click on the interface drop down to choose the interface (SATA, SAS, IDE, etc.) for the device.
Repeat for each device.
5.1. “Computer Type” must exist. To edit the Computer Type, click on the word "Edit" (green font and
underlined) above the words “Tested Configuration:”. Click on the Computer Type field. Choose the
Computer Type from the drop down choices. Click submit at the bottom of the screen.
5.2. “Mother Board Revision” must exist. To edit the Mother Board Revision, click on the word "Edit"
(green font and underlined) above the words “Tested Configuration:”. Delete the existing mother board
revision name in Mother Board Revision field. Type the new mother board revision name into the
Mother Board Revision field. Click submit at the bottom of the screen. Laptops may use Field
Replacement Unit numbers (FRUs) instead of motherboard revisions.
5.3. “BIOS/uEFI” version information must exist, including the version, and may list the manufacturer and
date (example: uEFI: YFG123 (4/5/2008) ). To edit the BIOS/uEFI information, click on the word
"Edit" (green font and underlined) above the words “Tested Configuration:”. Delete the existing
BIOS/uEFI in BIOS/uEFI field. Type the new BIOS/uEFI into the BIOS/uEFI field. Click submit at
the bottom of the screen.
5.4. “CPU” must exist. To change the CPU, a different CPU must be proposed. For instructions to propose
a new CPU see the section entitled “Proposing a Component in SBS” in this document. The only
170 SBS Users Guide

attributes that may appear are:
• quantity
• manufacturer
• type (model)
• speed
5.5. “RAM” must exist and may be listed as MB or GB. The minimum is defined by the operating system.
To edit the RAM, click on the word "Edit" (green font and underlined) above the words “Tested
Configuration:”. Delete the existing RAM in RAM field. Type the new RAM into the RAM field.
Click submit at the bottom of the screen.
5.6. “Ports and Bus Types” must exist. To add the Port and Bus types, click on the word "Edit" (green font
and underlined) above “Tested Configuration:”. Scroll down to the Ports and Bus Types section. Click
on the Ports and Bus Types field. Choose from the Ports and Bus Types listed in the drop down choices.
Type in the quantity for the selected Port or Bus Type into the Quantity field. Repeat for each
additional port and bus. Click submit at the bottom of the screen. The following can be listed.
• Quantity
• Type (e.g. PCI Express X16, PCI Express X8, etc.)
• Ports (e.g, serial, USB, etc.
5.7. “Video Adapter” must exist. Add the interface by clicking on the word "Edit" (green font and
underlined) above the words “Tested Configuration:”. Scroll down to the Video Adapter. Click on the
Interface field. Choose from the Interface Types listed in the drop down choices. Type in the quantity
for the video adapter into the Quantity field. Click submit at the bottom of the screen. To change the
video adapter, a different video adapter must be proposed. For instructions to propose a new video
adapter see the section entitled “Proposing a Component in SBS” in this document. The only attributes
that may appear are:
• manufacturer
• model
• quantity
5.8. SLED project certifications require that 2 radio buttons be set as follows:
• Desktop Effects Enabled - Yes or No will need to be chosen.
Yes- means that the Desktop Effects were enabled and functioned correctly. Choose No for SLES
12 (all SP).
• Power Management - Yes or No will need to be chosen.
Yes- means that the following power management tests all passed:
• SLED Workstations must pass Hibernate Test, Sleep Test, and CPU Frequency Test.
• SLED Laptops must pass Hibernate Test, Sleep Test, CPU Frequency Test, Brightness
Test, Brightness Keys Test, Lid Close Test, and Battery Test.
• For more information about the power management policy, please see the Yes Certified
System Test Kit Policy document located at:
c) Click submit at the bottom of the screen.
5.9. “Host Bus Adapter” must exist. Add the interface by clicking on the word "Edit" (green font and
underlined) above the words “Tested Configuration:”. Scroll down to the host bus adapter section.
Click on the Interface field. Choose from the Interface Types listed in the drop down choices. Type in
the quantity for the host bus adapter into the Quantity field. Click submit at the bottom of the screen.
To change the host bus adapter, a different host bus adapter must be proposed. For instructions to
propose a new host bus adapter see the section entitled “Proposing a Component in SBS” in this
document. The only attributes that may appear are:
• quantity
171 SBS Users Guide

• manufacturer
• model
• interface - This will need to be added.
5.10. “Hard Disk Drive” must exist. Add the interface by clicking on the word "Edit" (green font and
underlined) above the words “Tested Configuration:”. Scroll down to the hard disk drive section.
Click on the Interface field. Choose from the Interface Types listed in the drop down choices. Click
submit at the bottom of the screen. To change or add a hard disk drive, a different hard disk drive must
be proposed. For instructions to propose a new hard disk drive see the section entitled “Proposing a
Component in SBS” in this document. The only attributes that may appear are:
• quantity
• manufacturer
• model
• interface - This will need to be added.
5.11. If the CD/DVD is in the system and tested then it must be listed on the bulletin. If a CD/DVD is used
just for installing the OS, it is not required to be listed. Add the interface by clicking on the word "Edit"
(green font and underlined) above the words “Tested Configuration:”. Scroll down to the CD/DVD.
Click on the Interface field. Choose from the Interface Types listed in the drop down choices. Click
submit at the bottom of the screen. To change the CD/DVD, a different CD/DVD must be proposed.
For instructions to propose a new CD/DVD see the section entitled “Proposing a Component in SBS” in
this document. The only attributes that appear are:
• quantity
• manufacturer
• model
• interface- This will need to be added.
5.12. “Floppy Type” must exist if the system was tested (as opposed to only booted or installed) with a
floppy. Click on the floppy type field, choose from the drop down choices. If the floppy connects via
USB then select the “USB Floppy” submission choice instead of the “Floppy Type” choice. The “value
entry” should identify the make and model.
6. Add Configuration Notes as needed from our existing configuration notes.

6.1. If a configuration note is needed on the bulletin, then add by doing the following:
• Click on "Edit" (green font and underlined) above the Config Notes header
• Click on Add Config Notes.
• Click the Browse Notes button.
• Scroll through the existing notes for an applicable note.
• Click on the radio button next to the applicable note.
• Scroll to the bottom and click the OK button.
• If additional notes are needed, click on the Add Config Note button, the repeat steps c through f.
• Click submit at the bottom of the screen.
7. Verify the Adapters and Drivers section is accurate:

7.1. A driver must be listed in the “Adapters and Drivers” section for each LAN adapter, each host bus
adapter, and each video adapter. To add a missing driver, a different driver must be proposed. For
instructions to propose a driver see the section entitled “Proposing a driver for a Component in SBS” in
this document. Each LAN adapter, each host bus adapter, and each video adapter must list the
following driver information:
• Driver Type
• Driver File name
• Driver File date
• Driver File size
172 SBS Users Guide

• Driver Version
• Driver Checksum (Not always available)
7.2. All LAN adapters must be listed. To change the quantity click on the word "Edit" (green font and
underlined) above the words “Adapters and Drivers”. Scroll down to the LAN adapter. Type in the
quantity for the LAN adapter into the Quantity field. Click submit at the bottom of the screen. To add
or change the LAN adapter, a different LAN adapter must be proposed. For instructions to propose a
new LAN adapter see the section entitled “Proposing a Component in SBS” in this document. The
only attributes that appear are:
• Manufacturer
• Model
• Quantity
• Driver file information
7.3. Host Bus Adapter and Hard disk Drive must connect to at least one device in the Tested Configuration
section.
8. Move the submission to the Review State.

8.1. Click on Submit for Review at the top (white font on green background) or the bottom (black font with
green underline) of the bulletin web page.
8.2. Enter any information in the Communication field which the Engineer processing the bulletin will need
to know.
8.3. Enter explanations.
• Look for any exceptions that require a response, and enter responses as needed into the Response
field.
• Click on the Update Exceptions button at the bottom of the page.
• Repeat steps a and b until all errors and exceptions have a response and there are no more errors
to resolve.
8.4. Click on the Submit for Review button at the top of the page.
9. The submission will switch from the Open state to the Review state. The Developer Services Engineer will
review the submission and may ask for additional information.
173 SBS Users Guide

F.3 Needs Response State - Partner should do the following:
1. Log into SBS.

2. Choose a bulletin submission in the Needs Response state.
3. Click on the bulletin submission number (green font and underlined). This is listed under the Edit Submission
column.
4. Click on the words Submit for Review on the top (white font on green background) or the bottom (black font
with green underline) of the bulletin submission page.
5. Read in the Communications section for correspondence from the Developer Services Engineer.
6. Answer all questions and make all corrections to the bulletin submission as requested by the SUSE Engineer.
Type a response to all questions in the Communications section of the bulletin, then click done. For help to
enter or edit bulletin information see the instructions in section entitled “F.2 Open State - Partner should do the
following:”.
7. When all requests have been addressed re-submit the bulletin for review by clicking on the words Submit for
Review at the top (white font on green background) or the bottom (black font with green underline) of the
bulletin submission, then click on the Submit for Review button.
8. The bulletin submission status will change from the Needs Response state to the Review state. The
Developer Services Engineer will review the submission corrections and may ask for additional feedback.
F.4 Final Customer Review State - Partner should do the following:
1. Open a web browser to:

1.1. Log into SBS.
1.2. Select the bulletin submission under the Edit Submission column.
1.3. Validate all information on the Bulletin submission. Please ensure that all information on the
bulletin is completely accurate. This is the last chance to request changes to the bulletin. We do not
allow bulletins to be changed after they are released. We do not revoke or delete bulletins once they
are released.
1.4. To request a change to any information on the submission, please see #3 below.
2. To release the bulletin:

2.1. Click on the words Submit Bulletin for Release on the top (white font on green background) or the
bottom (black font with green underline) of the bulletin submission page.
2.2. Click on the Submit Bulletin for Release Button at the top of the web page.
2.3. The submission will switch from the Final Customer Review state to the Release Pending state.
2.4. The Release Pending is a temporary state that should only last a few minutes while the web server
updates its lists with the new bulletin.
2.5. After a few minutes the submission will automatically switch from the Release Pending state to the
Released state, but you must press F5 (Refresh) to update the browser with the new state.
3. If the submission requires additional information or corrections:
174 SBS Users Guide

3.1. Click on the words Submit Bulletin for Release on the top (white font on green background) or the
bottom (black font with green underline) of the bulletin submission page.
3.2. Enter correspondence into the communications field.
3.3. Click on Send Back to Reviewer for Response.
3.4. The submission will switch from the Final Customer Review state back to the Review state.
3.5. A SUSE Engineer will re-process the bulletin according to the requests in the communications
section.
F.5 Proposing a Component in SBS
The following steps are intended for proposing new computer components which do not exist in the SBS database
system. The new computer component will also be added to the next products.txt update. If a product already exists
in the SBS database, it will be a search result in the component check search on TC.
1. Click on "Edit" (green font and underlined) in the Tested Configuration or Adapters and Drivers section.
2. Scroll down to the missing component.
3. Click Add Proposed for the type of component.
4. Fill in the blank fields:
_________________________________________________________________________________
Note: All fields are required to be completed or the submission will be rejected as incomplete. This
will result in a needs response state for the submission.
_________________________________________________________________________________
4a. Enter the Product model in the Product name field.

4b. Click on the small square gray box containing 3 dots next to the Company Name field.
4b1. Enter the name of the company who manufactures the component (i.e. Intel, Adaptec, AMD, Nvidia,
etc. ).
4b2. Click Search
4b3. Click on the down arrow next to the Available Companies field.
4b4. Select the appropriate company from the drop down list.
4B5. Click Update.
4c. Enter the URL of the manufacturers webpage to the exact product being proposed. For legal
reasons we need to verify the component name and model on the manufacturers website.
_____________________________________________________________________________
Note: The Product URL must be to the exact component on the manufacturers website.
_____________________________________________________________________________
4d. Click Submit.

5. Repeat steps 2 through 4d for each component which needs to be proposed.
6. Once all proposed components have been added, click Submit at the bottom of the page.
175 SBS Users Guide

F.6 Configuration Notes
The configuration notes on a bulletin are used to communicate different testing circumstances.
Using the Existing SBS Configuration Notes

Please choose configuration notes from the existing SBS configuration notes. To access the existing configuration
notes do the following:
• Click on "Edit" (green font and underlined) above the Config Notes header.
• Click on Add Config Notes.
• Click the Browse Notes button.
• Scroll through the existing notes for an applicable config note. The config notes have category
filter check boxes which can be un-selected to narrow the config note listings. The config note
category filters are Installation, Virtualization, Power Management and Other.
• Click on the radio button next to the applicable note.
• Scroll to the bottom and click the OK button.
• If additional notes are needed, click on the Add Config Note button, the repeat steps c through f.
• Click the submit button at the bottom of the screen.
Separation of Configuration Notes

Sometime configuration notes are placed into the same config note box. Each configuration note needs to be
separated into its on config note box. Please separate all config notes into individual config notes. Follow the steps
below to separate the configuration notes:
1. Click on the word "Edit" (green font and underlined) above the config notes category.
2. Click on the "Add config note" button.
3. Enter the config note into the config note field.
4. Repeat steps 2 and 3 for each additional config note.
5. Click the submit button at the bottom of the screen.
Configuration Notes for Drivers which have been added to the SUT for Testing
The driver configuration note is needed to provide information for users to obtain the driver and duplicate the tested
configuration. We highly recommend that all drivers used in certification testing are downloaded from the SUSE
SolidDriver Program website. The SUSE SolidDriver Program drivers are built by SUSE and have a greater level of
support associated with them then non- SUSE SolidDriver Program drivers. Drivers from other locations may not be
supported in a customer escalation phone call. The SUSE SolidDriver Program drivers can be downloaded from:
http://drivers.suse.com/driver-process/pub/update/
The configuration note must include:

A. The driver name.
B. The URL download location for the driver.
C. The downloadable filename containing the driver.
D. Any instructions which an end user will need to install the driver.
The template config notes which are in the sample configuration notes are as follows:
SUSE SolidDriver Program compliant config note:

The <Driver Name> is SUSE SolidDriver Program compliant. The driver was installed from the following rpm:
176 SBS Users Guide

<driver rpm filename on drivers.suse.com>. This driver can be downloaded and installed after the SLES install. To
obtain the driver go to: http://drivers.suse.com/driver-process/pub/<exact file location>
SUSE SolidDriver Program non-compliant config note:

The <Driver Name> used during testing is not SUSE SolidDriver Program compliant. The driver was installed from
the following driver package: <driver rpm filename>. This driver package can be downloaded and installed after the
SLES install. To obtain the driver go to: http://<exact file location>
The <> are place holders for information. Please fill in the information between the brackets then remove the <>
after filling in the information.
Here is an example:
The igb.ko is SUSE SolidDriver Program compliant. The driver was installed from the following rpm: intel-igb-
1.3.19.3-1.x86_64.rpm and intel-igb-kmp-smp-1.3.19.3_2.6.16.60_0.21-1.x86_64.rpm. These drivers can be
downloaded and installed after the SLES install. To obtain the drivers go to:
http://drivers.suse.com/driver-process/pub/update/Intel/sle11sp1/common/x86_64/
Another driver config note example:

The fglrx.ko driver used during testing is not SUSE SolidDriver Program compliant. The driver was installed from
the following driver package:
ati-fglrxG02-kmp-pae(version:8.762_2.6.32.12_0.7-1(i586)) and x11-video-fglrxG02(version:8.762-1(i586)).This
driver can be downloaded and installed after the SLED install. To install the ATI driver, below steps are needed:
1.Yast-->Software Repositories Click "Add" in "Configured Software Repositories",select "Specify URL" and click
"Next". Enter the "Repository name" as "ATI driver" and "URL" as "http://www2.ati.com/suse/sle11sp1" in "Media
Type", and click "Next".
2. Yast-->Software Management. Change the filter to "Repositories",select the repository names "ATI" and install the
packages listed in "Available".
177 SBS Users Guide

F.7 Proposing a Driver for a Component in SBS
There may be situations when a driver used during testing needs to be added to the bulletin. There are 3 scenarios for
the missing driver.
I. The driver was detected but was not selected during the product information entry screens.
II. The driver was detected but was deleted from the System Information Entry on TC by the user.
III. The driver was not detected during the component check and as a result was not selectable during the System
Information Entry on TC. This is very unlikely but may happen if a hyperviser such as KVM is loaded for bare metal
testing.
The following steps are intended for proposing a missing driver for a computer component.
1. Click on "Edit" (green font and underlined) above the words Adapters and Drivers.
2. Scroll down to the component which is missing the driver.
3. Next to the File field click Add Proposed.
4. Fill in the blank fields:
_________________________________________________________________________________
Note: All fields are required to be completed or the submission will be rejected as incomplete. This
will result in a needs response state for the submission.
_________________________________________________________________________________
4a. Type the driver file name into File Name field.
4b. Type the driver file size into Size field.
4c. Type the driver file date into Date field.
4d. Type the driver version into Version field.
4e. Click on the File Type field. Choose the driver type from the drop down list.
4f. The Driver URL is an optional field. Your SUSE Engineer who is processing the bulletin submission will let
you know if the Driver URL is needed.
4g. Click Submit.
5. Repeat steps 2 through 4g for each missing driver which needs to be proposed.
6. Once all proposed drivers have been added, click Submit at the bottom of the page.
178 SBS Users Guide

F.8 Process for Creating a 3C Bulletin
For policy's regarding the 3C bulletins please refer to the Hardware Component Exchange Guide section in the Yes
Certified System Policies document located at:
To create a 3C bulletin follow the steps below.
2. Click on Create a 3C Bulletin.
3. Enter the bulletin number of the released non-3C bulletin to be referenced.
4. Click the Submit Query button. If the bulletin number which you are inputting is invalid or already a 3C
bulletin then the query will fail. The failed query will generate the following message: “Please enter an
Existing Bulletin Number that is not a referenced bulletin.”
5. Verify that the company name is correct.
5a. If the company name needs to be changed then click on the Change button.
5b. Enter the company name into the company search field.
The wild card % can be used to help search for the company name. For example Intel % will result in
the search result of Intel Corporation.
5c. Click on the Search button.
5d. Click on the Select Company drop down field to choose the company name.
5e. CPU and other computer pieces can also be changed. All changes must be in accordance with the
SUSE YES Certified System Test Kit Policies.
6. Verify that the product name is correct at the top of the summary. This field is editable.
7. Verify that the product description is correct at the top of the summary. This field is editable.
8. Click Next.
9. Verify that the components are correct. Edit as needed by clicking the change button associated with the
field.
10. Click Next.
11. Enter any further instructions into the field below above the Submit button.
12. Click Submit. The new 3C bulletin number will be displayed. The new 3C bulletin will be placed into the
company name queue in a review state. A SUSE engineer will process the bulletin in the order which it was
submitted.
179 SBS Users Guide

F.9 Process for Creating a SBS user account
The user will need access to the SBS Database to submit test results and generate Yes Certification Bulletins. In order
to access SBS a user account must be created. The following instructions are intended to guide the new user through
the process to create an SBS account. To create an SBS account do the following:
1. Open a web browser to the SUSE Bulletin System login screen. The URL is:
2. Click on the green button on the right labeled Create Account.
3. A screen entitled Create Account will open.
4. Enter your information into all of the fields on the Create Account screen then click on the Create Login
button located at the bottom of the screen.
5. Email to your SUSE Developer Services contact the following:
5a. Login username.
5b. Email address.
6. Once your SBS access rights are set up, an email will be sent to you by your SUSE Developer Services
contact.
F.10 Process for adding a new Company to SBS

In order to receive Yes Certification bulletins your company name and company information will need to be added to
the SBS Database. This will be the same company name and company information which you want listed on the Yes
Certification Bulletins. Please provide the following information to your SUSE contact:
1. Company name
2. Company URL
3. Address Line 1
4. Address Line 2
5. Address Line 3
6. City
7. State
8. Postal Code
9. Country
10. Phone
11. Toll-Free Phone
12. Fax
180 SBS Users Guide

G
Third Party Hypervisor Testing
Overview: Testing the Third Party Hypervisor is for companies who have their own hypervisor and would like to test
and Yes Certify SLES as a guest on their Hypervisor. A Yes Certification bulletin can be issued for Third Party
Hypervisors.
1 Follow the steps in section 2 to setup Testconsole.
2 Install one SLES 11 (latest SP) or one SLES 12 (latest SP) guest for the "Maximum Configuration Test" using the
OS installation instructions in the other sections of this Test Kit documentation. Give that SLES VMM guest as
many CPU's and as much Memory as your virtualization host can. For example, a server with 1 TB of RAM and 64
CPU's can divide the system resources allocating most resources to the VMM. The SLES VMM guest can be
assigned 1020 GB of RAM and 60 CPU's. The host is left with 4 GB of RAM and 4 CPUs. This is a preferred
situation for the "Maximum Configuration Test". When allocating system resources to the SLES VMM keep within
the SLES CPU and memory Technical limitations shown below.
________________________________________________________________________________________
Operating System Maximum # of Logical CPU's Maximum RAM
________________________________________________________________________________________
SLES 11 x86 (latest SP) 32 64 GiB
SLES 11 x86_64 (latest SP) 4096 64 TiB
SLES 12 x86_64 (latest SP) 4096 64 TiB
____________________________________________________________________________________________
IMPORTANT: The tests must be run individually top to bottom in order (except the "VMM Stress Tests", and
"Stress Tests" should be run at the same time in parallel) for the rest of the tests and test groups to run correctly.
The "Get VM1 Test Logs" must be run last in order to get all the test results.
____________________________________________________________________________________________
3 Using TestConsole, open a new project and select the "Virtualization-Full" project see project selection section.
4 Run all tests in the "Maximum Configuration tests" group (See "IMPORTANT" above). For example:
First double click on the VMM Install Test to run it. After the VMM Install Test completes then double click on the
Verify VMM Time Sync Setup test. After the Verify VMM Time Sync Setup test completes then double click on
the VMM Stress Tests.
After the VMM Stress Tests completes then double click on the Get Max Config Test Logs. Follow this process for
all testing. Then set up and run the testing for the multiple VM testing.
5 Reconfigure or reinstall the maximum configuration VM to be VM1 of the "Multiple VM Configuration tests". Then
install 2 or 3 additional SLES 11/12 VMs of your choice using the Test Kit documentation. Give your host
(hypervisor) the minimum number of required CPUs and Memory. Then divide the remaining memory and CPUs
181 Third Party Hypervisor Testing

between the Virtual Machine guests based on architecture (see the examples below), keeping in mind the
"CPU/Memory Technical pecifications" (shown above) for each guest kernel.
Example 1: 8 GB MEM, 16 CPUs:

With 3 guests, each guest gets 2 GB Mem, and 4 CPUs and the host gets 2 GB mem and 4 CPUs.
Example 2: 1 TB MEM, 64 CPUs:

With 4 guests, each x86 guest gets 16 GB Mem and each x86_64 guest gets 494 Gb and 15 CPUs. The host is left
with 4 GB mem and 4 CPUs.
6 If your virtualization platform supports the mounting of an optical interface, the VM2 guest should have the optical
drive mounted with test media.
7 Run all tests in the "Multiple VM Configuration Tests" group (See "IMPORTANT" above).
8 Put together a submission and submit it the same way you would a normal test submission as shown in the
documentation.
182 Third Party Hypervisor Testing

H
Downloading SLE Products and Patches
The same account username which is used to access SBS is also used to download SLE products and patches.
To access the download site for the SUSE Operating System do the following:
1. Open a web browser to https://download.suse.com/index.jsp
2. Click on Login at the top right of the webpage.
3. Enter your username and and password, then click GO.
4. Click on the drop down fields to select OS product criteria, then click on the Submit Query button.
5. Click on the OS product in the bottom search results which best matches your criteria. This will open the
web page for that OS product.
6. If this is the OS product which you are looking for then click on the proceed to download (red font) button on
the upper right side of the webpage.
7. If prompted, login.
8. If prompted, answer the questionnaire then click submit.
9. Click on the download (red font) button on the right side of the dvd size. DVD 1 is the OS installation DVD
(the binary packages). DVD2 contains the source code.
10. Follow the in browser on screen prompts to save the product OS iso file onto your computer drive.
To access and download SUSE patches do the following:
1. Open a web browser to SUSE.com

2. Click on Login at the top right of the SUSE webpage.
3. Enter your username and password, then click GO.
4. Click on Support → Downloads → Patches. The patches search page will open.
5. Click on the drop down fields to select the patch criteria or type into the Quick Select field then click on the
Search button. The search results will be listed at the bottom. Mousing over a patch will display information
about the patch.
6. Click on the patch in the bottom search results which best matches your criteria. This will open the web page
for that patch.
7. If prompted, login.
8. If prompted, answer the questionnaire then click submit.
9. Click on the proceed to download (red font) button on the upper right side of the webpage.
10. Click on the accept (red font) button.
11. Click on the download (red font) button on the right side of the dvd size.
12. Follow the in browser on screen prompts to save the patch iso file onto your computer drive.
____________________________________________________________________________________
Note: If your login rights are not working then contact your SUSE Yes Certification support engineer.
____________________________________________________________________________________
The Subscriber Portal is available to request software registration codes and download software.
To access the Subscriber Portal do the following:
1. Open a web browser to the Subscriber Portal to: https://download.suse.com/index.jsps/portal/spc
2. Login at the Please sign in screen.
183 Downloading SLE Products and Patches

3. Click on Professional Resource Suite Electronic – Partner (in the blue square box at the bottom).
4. The choices on this screen will include Download Software, Request Software Registration Codes and more.
To request software registration codes do the following:
1. Click on Request Software Registration Codes.

2. Locate the software to request registration code for.
3. Click on request a code.
4. The code will be sent to you via email. The code will activate the software for 1 year.
To download software do the following:
1. Click on Download Software.

2. Locate the software desired to be downloaded, then click on it. The download page for the software will
open.
3. Click on the proceed to download (red font) button on the upper right side of the webpage.
4. Click on the download (red font) button on the right side of the dvd size.
5. Follow the in browser on screen prompts to save the software iso file onto your computer drive.
___________________________________________________________________________________
Note: If your login rights are not working then contact your SUSE Yes Certification support engineer.
___________________________________________________________________________________
184 Downloading SLE Products and Patches

I
ARM Certification
The testing for the ARM systems will be the same as a typical SLES system. Kdump is not supported on the ARM
system. For SLES installation instructions on an ARM system refer to the online SLES documentation. The online
SLES documentation is located at:
185 ARM Certification

(en) 6 April 2007
J
Revision History
_____________________________________________________________________________________
Date Description
October 2017 Removed hyper-threading note from Xen opening section. Changed section
2.34 step 4a.
August 2017 Added small changes, mostly refinements. Added some steps to the end of the
TC installation. Removed some steps from the manual SLED test kit installation,
the test kit now performs the steps.
July 2017 Updated for SLE 12 SP3. Added the following new tests: Memory Persistence
Test, Persistent Memory Test, Error Check Test. Added information for time sync
test failure.
October 2016 Testing section – unified formatting added for consistency. Test overview label
added to many tests. Small changes in testing section for clarification and
alignment. Added instructions for VMM RAM. Updated the USB drive & Firewire
drive formatting instructions. Removed XEN, KVM and Third party hyperviser
USB pass through testing information. Added ARM section.
September 2016 Moved SLE product download instructions to it's own new section (H). Added
clarity for the VM USB testing. VM clarification for RAM setup for SLES 11
added. Changes in section B. Other small word changes were made. Changes
in section B. Changes to manual install for SLES and SLED. Small corrections
in the TC testkit install. In some places replaced the word running with the word
starting. Some section titles have been changed.
August 2016 More clarifications added throughout the testing section. Removed the SLED 11
SP 4 wireless NIC enablement instructions from the verify wireless NIC section.
Changed/corrected the loop mount instructions for the Testkit installation in
multiple sections. Removed section A.8.2 desktop effects issues.
July 2016 Updated sections 4.1c and 5.2c for the new capabilities of the install_vm. Added
KVM and Xen require 1 USB storage device. Changed the SLED 12 SP2
manual installation instructions to match SLES 12 SP2 (beta4). Some changes
to the order of tests. Clarifications added throughout the testing section.
Clarification added to section 2.5.2 Updating with Other Media.
June 2016 Changed the XEN OS Certification tables and added the VMM OS tables. The
XEN and KVM sections were changed throughout and now includes the VMM
guest instructions.
May 2016 Changed title for 7.6 Testkit. Removed the SLED 11 project listings. Replaced
SLES 11 SP3 with SLES 11 SP4 on the TC. Removed the SLED 11 SP4
section. Replaced SLES 12 SP1 with SLES 12 SP2. Removed Section G
Network Manager Configuration Guide which was for SLED 11. Removed the
Desktop effects test. Re-ordered the tests to match the projects. Replaced
KVM and XEN projects with new Virtualization Project. Removed the SLED 11
information through out the doc. Small clarifications added to TC install to
accommodate SLES 11 SP4. Some changes and clarification added to Testkit
186 Revision History

installation on the SUT section.
April 2016 Added OS version requirements clarification for the PCI Pass-Through
and SR-IOV testing through out the doc.
March 2016 Added information to product description instructions. Changed Video, LAN,
HBA and Storage Device Information to re-add a deleted device. Changes in the
component check section to match Test Kit. Continued formatting and font
changes through out the documentation for consistency. Changed Testkit to Test
Kit throughout the documentation. Changed most Legal notice info from Novell
to SUSE. Re-ordered the tests to match the testing projects which are on TC.
February 2016 Added clarity to section F9 and F10. Added new VMDP URL. Added clarity and
steps to the TC testkit installation section. Added sysstat to the TC installation
list. Changed the loopmount location for the testkit installation in the TC
instructions. Formatting and font changes through out the documentation for
consistency. Added more information to section B.
January 2016 Added “Company not selected” to the instructions in section 2.11.2. Some
changes in XEN and KVM sections. Changes made through out chapter 1.
Removed section 1.8 Lab Verification. Reduced the new section 1.8 - Lab Site
Inspection. Added section 1.3 - New Companies and New User Access. Added
more info to section 2.39 Get Test Logs Test important note.
December 2015 Added Section F10. Added Section H, Third Party Hypervisor Project.
October 2015 Updated Doc to SLE 12 SP1. Added section A.23 KVM USB Pass Through
Setup. Removed AppArmor from A.12.2.
September 2015 Modified the Testkit installation instructions for TC and the OS DVD install
sections. Changes were made to section 3.4 “Manually Installing the Test Kit on
the SLED 12 SUT”.
July 2015 Updated the Virtual Machine Driver Pack URL in all 3 locations. Changed fonts
size in section F8 to match the rest of the doc. Minor fixes through out the doc.
Corrected PCI Pass-thru to PCI Pass-through. Corrected pass with warning
throughout the doc to PASS w/WARNING to match the testkit actual message.
March 2015 The doc revision changed to 7.4 to match the new testkit version. Removed all
instructions for Windows server 2003. Replaced SLE 11 SP3 SUT with SLE 11
SP4 SUT. Added section F.9 Process for Creating an SBS account. Added
section F.10 Process for downloading SLE products and patches. Minor
changes for clarification.
January 2015 Added clarity for SLES 12 to step 5 in the Xen "For a ParaVirtualized SLES OS
Network installation do the following (Recommended)" section. Added
information about the config note category filters to F.6 Configuration Notes
Step d).
December 2014 Added new Xen screenshot to section 2.8.
November 2014 Added Troubleshooting section for Sleep and for Hibernate.
October 2014 More changes and refinements in the SR-IOV instructions. Removed vsftpd
from SLED 11 SP3 installation instructions. Added section A.20 IPv6
Information. Added section A.3.2 TestConsole Locks Up or has Blank
Screen during Testing. Added section A.4.2 Time Sync Test Fails or Time
Sync Verify Test Fails. Added a note to beginning of section 2.4.
September 2014 Small changes in SR-IOV sections. Added SLES 12 VM wizard installation
section 4.1b Installing a Xen Virtual Machine. Added the SLE 12 Projects
to the project listing page. Some changes to the project descriptions were

made. Many changes to KVM SR-IOV instructions.
August 2014 Checked and updated URL's as needed. Notable change: Replaced
download.novell.com with https://download.suse.com/index.jsp for SUSE
product downloads. Made sure that the URL's would go to the link when clicked
on in this documentation. Many changes in the KVM section. Updated all VM
IP addresses to match the 7.3 testkit. Changed capitalization from XEN to Xen
in order to match the SUSE online Documentation. Added 2.33.5 Verify PCI
Pass Through or SR-IOV Setup test with instructions. Added SRIOV for XEN
instructions. Many rewrites and additional instructions added to section “F.2
Open State -`Partner should do the following:”. Rewrote section “F.7 Proposing
a Driver for a Component in SBS”. Other changes and clarifications made to the
SBS Users Guide. Removed from chapter 2 the “This section covers the
following topics:” portion. Removed from chapter 1 the “This section covers
the following topics:” portion. Updated the virtual machine driver pack
URL's to 2.1 driver pack location. Corrections and clarification added to
section 2.11.x. Replaced mount – o loop/<iso file name.iso> <Enter> with
mount /<Path>/<iso file name.iso> /mnt <Enter>. Many changes to the
SR-IOV instructions. Replaced XEN PCI Pass-Through instructions with
updated instructions. Moved section “C.7 Submitting Test Results” to
become section “2.40 Submitting Test Results” for improved instruction
flow. Added SLES 12 wireless NIC setup instructions to section 2.33.3
Verify Setup – Wireless NIC. Removed Pure-ftpd from SLED 11 SP3
manual installation instructions and added vsftpd. Added mgetty to SLES
11 SP3 installation instructions.
July 2014 Changed KVM CPU over committing for windows to be the same as SLES.
Additional minor changes were made.
June 2014 Changed vsftp to vsfptd for TC install. Added KVM CPU over committing
instructions. Removed Print Server from TC patterns list. Removed the
NetWare guest from the Xen section. Added Xen CPU over committing
instructions. Added SR-IOV for KVM setup instructions.
May 2014 Updated the project file-name instructions to match the test kit enhancements.
Added SLED 12 manual install static IP address configuration instructions.
Added additional SLED 12 installation instructions. Minor changes made to
section 2.11. Removed KVM patterns from SLES 11 SP3 manual installation
software list. KVM patterns and Xen Patterns are not included in the SLES 12
manual installation instructions.
April 2014 Began adding the SLED manual installation instructions. Made changes to the
SLES install. Added nmap and vsftp toTC install. Changes made to manual
test kit install instructions for SLES 11 & 12.
March 2014 Continued to add SLE 12 to doc sections. Changed IP address scheme
according to the new 7.3 test kit (example: 10.2.1.1 became 10.1.2.1). Updated
the IP addresses in the graphics. Changed the USB formatting instructions,
removed the SLES 10 parts. Added some clarity to the interface information in
SBS section. Added java-1_7_0-ibm package to the TC install instructions.
February 2014 Changed the DOC from 7.2 to 7.3. SLE 12 was added. Changed TC to have
OS SLES 11 SP3. Changed PLDP references to SUSE SolidDriver Program.
October 2013 Added information to component check troubleshooting section. Added

information to remove partitions or GPT to troubleshooting section. Changed
and reduced the manual SLED steps for partitioning the hard disk drive. Also
clarified some of the manual SLED installation steps. Added: Product and
report information entry section to troubleshooting. Added section: IP address
issues to Kdump troubleshooting section. Made changes to SLED testing
instructions to include wireless workstations.

September 2013 Added information to section 2.2.2 step 2. Added information to component
check test.
August 2013 Added file name details to PXE boot paravirtualization guest install steps.
Explained that ISO image directory cannot have a space in the directory name.
Small grammatical corrections.
July 2013 Added steps to change the DHCP available Address range on TC during
install. Corrected step numbering in section 2.4. Rewrote the SLED 11
SP3 DVD manual install HDD partitioning instructions to create enough
space on / (root) for running the kdump test.
June 2013 Added a instructions to restore deleted LAN, HBA, and video drivers/adapters.
Changed NetWare VM and Windows VM IP addresses to match the test kit
project. Changes made to the PCI-through sections.
May 2013 Labeled PCI Pass-Through as recommended, but optional. Made changes to
the Hibernate, Sleep, and Kdump test instructions. Corrected some URL 's.
Made changes to section 2.11.1 System Information for the BIOS information
entry. Added config note creation steps inline to section F.2 Open State. Also
rewrote parts of section F.2 Open State. Added loop mount instructions to the
manual CD test kit installs. Removed the raid configuration steps in the SLES
installation on TC. Clarification added to section 2.34 Optical Device Tests
Overview.
April 2013 Added Troubleshooting section A.1.1- Removing the ELIO Boot Tables.
Removed Xen non-VT table. Removed SLE 10 Host from Xen figure 4.1.
Added Windows Server 2012 Test Kit installation instructions to the Xen section.
Added using kISO's section. Updated the VMDP URL. Added Windows Server
2012 Test Kit installation instructions to the KVM section. Section F.2 “Open
State” has been re-organized and some parts have been re-written. Desktop
effects and power management criteria have been added to section F2. Added
information to tests which are required to pass for power management to be
listed.
March 2013 Added SUSE logos to cover page. Reordered and rewrote section 2.6
through section 2.11 to match the changes in the Test Kit. Edited the manual
SLES install to match the new install screens (minor changes). Changed the TC
OS to be SLES 11 SP2. Removed the instructions to remove a raid disk drive
before starting the stress tests.
January 2013 Removed the Standby Test. Removed Parallel port test. Renamed install test
to be Validate install test. Changed passwords to suse. Changed doc cover
page name to include SUSE. Changed Floppy test information, it is now grayed
out in the project. Changed Bus information to Bus and Port types information.
Changed BIOS Information to BIOS/UEFI Information. Added PCI
Pass-Through sections for Xen and KVM. Removed SLE 10 SP4.
October 2012 Added to and reorganized kdump information in the troubleshooting section.
Added the Windows 2008 (all releases) VM file sharing steps. Added section F8
Process for creating a 3c bulletin. Added section F7 – Proposing a driver in
SBS. Combined section A15 with section A16. Added in a note that Standby test
is not supported on SLED 11. Replaced reference to NBS with SBS.
September 2012 Edited section F - Removed product search, references to NBS and to Novell.
Added SBS URL . Through out the doc - changed some of the Novell
references to SUSE.
April 2012 Changed the External Monitor Test to only apply to Laptops/notebooks. Added
information to get testlog tests. Re-arranged and re-numbered red topic listings
in section 2. Modified section 2.34.4 for 16 NICs.
March 2012 Updates the driver section (D). Arranged Xen OS tables so the Fully virtualized

guest is listed first. Added some clarifications as requested.
February 2012 Many clarity changes and improvements. Moved serial port test to be run after
the component check test. Added additional serial port debugging information.
Added the Network Manager Configuration Guide.
January 2012 Small changes for clarity. Added the change that the first VM must be installed
using a DVD in order for the optical test to work correctly.
December 2011 Removed the virtio_net driver info from KVM section as requested by MW.
November 2011 Removed the option to get PLDP drivers from:

http://drivers.suse.com/driver-process/staging/pub/update/
Removed the router and gateway steps from SLES 10and 11 manual setup.
September 2011 Added instructions for the xen and KVM optical media testing. Added detailed
instructions for choosing the device interface in NBS.
August 2011 Removed the Devices tab section.
March 2011 Made changes to the manual OS installation section. Made changes to the XEN
testing matrix table. Added instructions in section F for configuration notes.
February 2011 Rewrote the virtual machine (Xen and KVM) test kit install to be through the TC.
Many KVM and XEN installation changes have been made.
January 2011 Modified the documentation for the new PXE installation. Removed FS4 from
the documentation. Removed SLES 9 and NLD from the documentation.
Added nmap for SLE. Removed nmap from SLED. Removed outdated portions
of the troubleshooting section.
November 2, 2010 Updated NFS mountpoint instructions in A.7.2. Updated many URL's.
September 1, 2010 Added clarification for get test logs test. Added overall hard drive size needed
on SUT for KVM testing. Added KVM guest pldp driver information. Added
more information for mincom usage. Added LAN troubleshooting information.
Removed SLES 9 SP4 from KVM section.
July 2010 Added clarification of KVM NIC and IP addresses. Also Added troubleshooting
section 13.
April 2010 Added KVM testing information
June 2, 2009 Added clarity to proposing adapters in the component check.
June 1, 2009 Added NBS users guide to the test kit documentation (Appendix section F).
May 2009 Refined all sections. Made changes to reflect test kit alterations. Added
wireless NIC configuration details.
January 8, 2009 Added/modified sections for SLES 11.
December 2007 Added SPident installation requirement for SUT (SLES 10 sp1, NLD 9 and SLED
10)
November 2007 Added unixODBC install to TC, FS4 and SLED 10 sp1 and SLES 10 SP1 install
October 2007 Added steps for multiple projects on TC to appendix. Modified the XEN
hardware tables.
September 2007 Added install script instructions. Moved manual install to apendix.
August 22, 2007 Added PV driver information & instructions, made changes to XEN windows

installation instructions, made slight modifications to the power management
May 8, 2007 Version 6.1

September 8, 2006 Updated USB Test.
August 31, 2006 Updated Troubleshooting section. Updated SLED 10 install. Updated Serial
Port Test.
August 24, 2006 Updated Xen, NLD 9, and SLES instructions.
August 15, 2006 Added Updating the Product.txt file.
August 11, 2006 Updates to SLES 10 installation.
August 10, 2006 Updates to SLES and SLED installation.
August 8, 2006 Updates to SLED and NLD 9 test section.
August 1, 2006 Updates to Xen procedures. Updates to CD and DVD tests.
July 17, 2005 Added SLES 10 and SLED 10 certification tests.
March 1, 2006 Updated Section 2.21.7, “NIC Test Setup,” on page 56 and Section 2.21.8,
“Router Test Setup,” on page 57. Updated format.
November 16, 2005 Updated 3C (Certified + Certified = Certified) The ability was added to
interchange certified components on System bulletins. NIAS (WAN) test
was removed from the kit. Reduced test suite for Linux was added.
July 22, 2005 Updated the following tests in the Linux Test Suite: CD-ROM/DVD Test,
Serial Port Test troubleshooting, and Hard Disk Test.
Added OES Bulletins based on NetWare 6.5 SP3 testing-NsPolicy 07082005,
Version 1.0 and OES Bulletins based on SLES 9 SP1 testing-NsPolicy
03212005, Version 1.0 to the Policies section.
June 28, 2005 Updated instruction for entering the product description.
June 16, 2005 Updated instructions for updating the Products.txt file.
June 2005 Updated SLES 9 and NLD 9 installation instructions. Updated USB Test
information.
March 16, 2005 Updated Network Client Test Suites.
March 8, 2005 Added instructions for upgrading TC and FS4 to SP 1. Updated instructions
for installing OES.
February 26, 2005 Updated the Linux USB test and the NLD 9 Client test.
February 23, 2005 Updated NetWare, Linux, and NLD 9 test suites.
February 1, 2005 Updated NetWare and Linux test suites.
___________________________________________________________________________________

SUSE Yes Certification Kit

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SUSE Yes Certification Kit

Hochgeladen von

Copyright:

Verfügbare Formate

SUSE Yes Certification Test Kit

October 12, 2017 SYSTEM TEST TOOLS FOR SUSE®

Certification Policies and Process....................................................................................................12

Linux Test Suite ...............................................................................................................................15

2.1 Configuring the Hardware..................................................................................................15

3.1 Configuring the Hardware for SLED 12 SP3 Testing........................................................83

Xen Virtual Machine Tests...............................................................................................................89

4.1a Installing a Xen Virtual Machine......................................................................................92

Kernel-based Virtual Machine Tests...............................................................................................110

5.1 Configuring the KVM server............................................................................................110

Manually Installing SLES 12 or SLES 11 .....................................................................................126

6.1 Manually Installing SLES 12 SP3 on SUT.......................................................................126

Troubleshooting and Help .............................................................................................................136

A.1 Installation Issues.............................................................................................................136

Uninstalling the Test Kit from a Linux System .............................................................................158

Adding Drivers to the SUT............................................................................................................164

Identifying Vendor Device Ids .......................................................................................................167

SBS Users Guide...........................................................................................................................168

F.1 Creating a Bulletin in SBS using a Bulletin Submission File ..........................................168

Third Party Hypervisor Testing......................................................................................................181

Downloading SLE Products and Patches.......................................................................................183

ARM Certification .........................................................................................................................185

11 About This Guide

1.2 Certification Policies Location

1.3 New Companies and New User Access

1.4 Certification Process Overview

12 Certification Policies and Process

1.5 Test Results and Audits

1.6 Support Information / URL Addresses

• YES Certified Systems Test Kit for Linux (https://www.suse.com/partners/ihv/yes/system-test-tools-for-suse-

13 Certification Policies and Process

• Current copy of the System Test Kit

1.8 Lab Site Inspection

14 Certification Policies and Process

2.1 Configuring the Hardware

✔ Minimum SLE requirements must be met on the SUT hardware

✔ A CD with at least 600 MB of data, for systems with CDROM drives.

15 Linux Test Suite

Minimum Requirements for TestConsole (TC)

✔ 1 Monitor with minimum 800x600 or better resolution.

16 Linux Test Suite

Figure 2-1 Configuration for the SLES tests with 16 NICs

Figure 2-2 Configuration for the SLES tests with 2 NICs

17 Linux Test Suite

For systems with one NIC.

18 Linux Test Suite

2.2.1 Installing SLES 11 SP4 on TC

19 Linux Test Suite

20 Linux Test Suite

21 Linux Test Suite

eth1 10.1.2.2 NIC2 2 eth1 10.1.2.1 NIC2

eth2 10.1.3.2 NIC3 3 eth2 10.1.3.1 NIC3

eth3 10.1.4.2 NIC4 4 eth3 10.1.4.1 NIC4

22 Linux Test Suite

19j6 Enter 255.255.255.0 for the Netmask.

23 Uncheck Clone this system for Autoyast.

23 Linux Test Suite

2.2.2 Installing the Test Kit on TC

1 Log in to the SLES 11 SP4 TC as root.

24 Linux Test Suite

2.2.3 Setting Up the DHCP/PXE Server on TC

25 Linux Test Suite

1 Obtain an installation DVD of the desired SLE version.

2.2.4 Adding ISO Images to the PXE Menu on TC