When you check the compliance of ESXi hosts against an upgrade baseline, vSphere Lifecycle Manager runs a precheck script and provides informative messages in the in the bottom pane of the vSphere Lifecycle Manager compliance view. The messages notify you about potential problems with hardware or third-party software on the host, and configuration issues, which might prevent a successful upgrade to ESXi 7.0.
The messages that vSphere Lifecycle Manager provides correspond to error or warning codes from running the host upgrade precheck script.
For interactive installations and upgrades performed by using the ESXi installer, the errors or warnings from the precheck script are displayed on the final panel of the installer, where you are asked to confirm or cancel the installation or upgrade. For scripted installations and upgrades, the errors or warnings are written to the installation log.
vSphere Lifecycle Manager displays scan result information in the bottom pane of the vSphere Lifecycle Manager compliance view. To see the original errors and warnings returned by the precheck script during an vSphere Lifecycle Manager host upgrade scan operation, review the vSphere Lifecycle Manager log file.
|Scan Result Message invSphere Lifecycle Manager||Description|
|Host CPU is unsupported. New ESXi version requires a 64-bit CPU with support for LAHF/SAHF instructions in long mode.||
This message appears if the host processor is 32-bit and does not support required features.
The corresponding error code is 64BIT_LONGMODESTATUS.
|Trusted boot is enabled on the host but the upgrade does not contain the software package esx-tboot. Upgrading the host will remove the trusted boot feature.||This message indicates that the host upgrade scan did not locate the esx-tboot VIB on the upgrade ISO.
The corresponding error code is TBOOT_REQUIRED
|VMkernel and Service Console network interfaces are sharing the same subnet subnet_name. This configuration is not supported after upgrade. Only one interface should connect to subnet subnet_name.||
Warning. An IPv4 address was found on an enabled Service Console virtual NIC for which there is no corresponding address in the same subnet in the vmkernel. A separate warning appears for each such occurrence.
The corresponding error code is COS_NETWORKING.
|New ESXi version requires a minimum of core_count processor cores.||The host must have at least two cores.
The corresponding error code is CPU_CORES.
|Processor does not support hardware virtualization or it is disabled in BIOS. Virtual machine performance may be slow.||
Host performance might be impaired if the host processor does not support hardware virtualization or if hardware virtualization is not turned on in the host BIOS. Enable hardware virtualization in the host machine boot options. See your hardware vendor's documentation.
The corresponding error code is HARDWARE_VIRTUALIZATION.
|Insufficient memory, minimum size_in_MB required for upgrade.||
The host requires the specified amount of memory to upgrade.
The corresponding error code is MEMORY_SIZE.
|Host upgrade validity checks for file_name are not successful.||This test checks whether the precheck script itself can be run.
The corresponding error code is PRECHECK_INITIALIZE.
|The host partition layout is not suitable for upgrade.||
Upgrade is possible only if there is at most one VMFS partition on the disk that is being upgraded and the VMFS partition starts after sector 1843200.
The corresponding error code is PARTITION_LAYOUT.
The file /etc/vmware/esx.conf must exist on the host.
This message indicates that the file /etc/vmware/esx.conf is either missing, or the file data cannot be retrieved or read correctly.
The corresponding error code is SANE_ESX_CONF.
|The host does not have sufficient free space on a local VMFS datastore to back up current host configuration. A minimum of size_in_MB is required.||
The host disk must have enough free space to store the ESXi 5.x configuration between reboots.
The corresponding error code is SPACE_AVAIL_CONFIG.
|The upgrade is not supported for current host version.||
Upgrading to ESXi 7.0 is possible only from ESXi 6.5 and ESXi 6.7 hosts.
The corresponding error code is SUPPORTED_ESX_VERSION.
|Unsupported devices device_name found on the host.||
The script checks for unsupported devices. Some PCI devices are not supported with ESXi 7.0.
The corresponding error code is UNSUPPORTED_DEVICES.
|Host software configuration requires a reboot. Reboot the host and try upgrade again.||
To ensure a good bootbank for the upgrade, you must reboot the hosts before remediation.
The corresponding error code is UPDATE_PENDING.
In an environment with Cisco Nexus 1000V Distributed Virtual Switch, vSphere Lifecycle Manager displays different messages in different situations. For details, see Host Upgrade Compliance Messages When Cisco Nexus 1000V Is Present.
If Cisco's Virtual Ethernet Module (VEM) software is found on the host, the precheck script checks if the software is part of the upgrade as well, and that the VEM supports the same version of the Virtual Supervisor Module (VSM) as the existing version on the host. If the software is missing or is compatible with a different version of the VSM, the script returns a warning and the scan result indicates the version of the VEM software that was expected on the upgrade ISO, and the version, if any, that was found on the ISO.
The corresponding error code is DISTRIBUTED_VIRTUAL_SWITCH.
|The host uses an EMC PowerPath multipathing module file_name to access storage. The host will not be able to access such storage after upgrade.||
The script checks for installation of EMC PowerPath software, consisting of a CIM module and a kernel module. If either of these components is found on the host, the script verifies that matching components (CIM, VMkernel module) also exist in the upgrade. If they do not, the script returns a warning that indicates which PowerPath components were expected on the upgrade ISO and which, if any, were found.
The corresponding error code is POWERPATH.