ESXi Upgrade may fail with the error: Host Does Not Fulfill Suspend To Memory Hard Dependencies
search cancel

ESXi Upgrade may fail with the error: Host Does Not Fulfill Suspend To Memory Hard Dependencies

book

Article ID: 429857

calendar_today

Updated On:

Products

VMware vSphere ESXi 8.0

Issue/Introduction

During ESXi host upgrade or patch remediation using vSphere Lifecycle Manager (vLCM), the validation process may fail with the following error:

"The host does not fulfill the following Suspend To Memory hard dependencies."

This error occurs during the pre-check phase when the "Suspend to Memory" (S2M) and Quick Boot features are enabled. While S2M is designed to speed up upgrades by keeping Virtual Machines in RAM instead of evacuating them via vMotion, it requires specific hardware and firmware compatibility. If these "hard dependencies" are not met, the upgrade process is blocked.

Cause

The "Suspend to Memory" feature allows VMs to stay on the host during a reboot, significantly reducing downtime. However, it relies on Quick Boot technology, which has the following requirements:

  1. The server platform (BIOS/UEFI) or installed PCI devices do not support the S2M state.

  2. S2M is restricted to patching operations (e.g., Hot Patches, Express Patches). It is not supported for major upgrades (e.g., upgrading from ESXi 8.0 U2 to 8.0 U3).

  3. Secure Boot or TPM configurations may interfere with the Quick Boot handoff.

Resolution

Workaround : 

Option 1: Disable Quick Boot and Suspend to Memory (Recommended)

If the hardware does not support S2M or version upgrade is being performed, these features must be disabled to proceed with a standard full-reboot upgrade.

  1. Log in to the vSphere Client.

  2. Navigate to Lifecycle Manager > Settings.

  3. Select ESXi Host Settings or go to the specific Cluster > Updates tab.

  4. Click Edit on the Remediation Settings.

  5. Under the Host Quick Boot section:

    • Uncheck "Enable Quick Boot."

    • Ensure the "VM Lifecycle" setting is set to vMotion or Power Off instead of "Suspend to Memory."

  6. Click Save.

  7. Run the Remediation Pre-check again and proceed with the upgrade.

Option 2: Verify Hardware Compatibility for S2M

If the S2M feature is required, ensure the environment meets the following requirements:

  1. Check Compatibility List: Verify the server model is on the Supported Systems in VMware vSphere with Suspend to Memory feature

  2. Validate Driver/Firmware: Ensure all PCI device drivers are compatible with Quick Boot.

  3. Run Pre-check: Use the loadESX.sh -v command via the ESXi Shell to check for Quick Boot compatibility on the specific host.

Powered by Wolken Software