Return codes of capacity scans on virtualization hosts

Edit online

If the capacity scan that is run by using the Run Capacity Scan on Virtualization Hosts task fails, an error code that indicates why the scan failed is returned. The code is presented in the results of the Status of Capacity Scan on Virtualization Hosts analysis. Check what is the possible cause of scan failure that is indicated by each code and how to solve the problem.

Table 1. Return codes of capacity scans on virtualization hosts
Return code Possible cause and solution
0 No errors.
20 Unsupported virtualization type. To solve the problem, perform the following steps:
  • Verify that the computer on which you ran the task is a virtualization host. If it is not, you do not need to run the task on this computer.
  • Verify that the computer runs on a supported virtualization. If the virtualization is a supported version of PowerKVM, KVM x86, Citrix Hypervisor (formerly XenServer), contact IBM Support. If it is a different type of a supported virtualization, configure VM managers to collect capacity data from these hosts. For more information, see: Adding VM managers in local and central mode.
30 KVM virtualization architecture could not be recognized. KVM virtualization was detected, but testing the virsh command to determine whether the architecture is x86 or Power failed. Contact IBM Support.
40 Determining the number of processor sockets or cores failed. The returned result is not a number. Contact IBM Support.
50 No valid host UUID could be retrieved by using the xe, dmidecode, and xl command. Verify that the UUID of the computer is correctly returned by SMBIOS. If it is not correctly returned, contact the hardware vendor to solve the problem.
Other codes If other codes are returned, check the run_vtech_scan.log log file to learn running which command returned the code. The log file is in the installation directory of the BigFix® client, by default: var/opt/BESClient/LMT/vtech/run_vtech_scan.log.