Failure due to memory tiering

[gdh2024-gdh]

Describe the bug

Deploying Holodeck to a Minisform MS-A2 with memory tiering enabled fials. VMs being deployed will not power on with the following error

Failed - This type of VM is not supported when software memory tiering is enabled.
This type of VM is not supported when software memory tiering is enabled.
An error occurred while parsing scheduler-specific configuration parameters.
Module 'MemSchedEarly' power on failed.
Failed to start the virtual machine.

Reproduction steps

1.New-HoloDeckInstance -Version 9.0 -InstanceID 'demo' -vSANMode ESA -DepotType Offline -ManagementOnly
2.
3.
...

Expected behavior

expected deployment to succeed

Additional context

No response

[gdh2024-gdh]

holodeck logs just repeat the following:

SSH service on 10.1.1.101 is not responding, Trying after 10 seconds

Since the VM never powers on and can't, holodeck deployment cannot continue

[hirohiro43]

Currently, nested ESXi with ESXi 9.0 memory tiering is limited, so you will need to run it on 8.0 memory tiering.

[dhruv-tyagi-broadcom]

This is expected behavior as memory tiering is not supported on ESX 9.0.

Unclear what this means - you will need to run it on 8.0 memory tiering. - Are you suggesting we deploy ESX 8.0 to deploy VCF 9?

[hirohiro43]

Yes, I suggest ESXi 8.0 as a deployment target for nested VCF 9.0.
It was unstable but I was able to deploy it.

[dhruv-tyagi-broadcom]

This is supported today. You can deploy VCF 9 via Holodeck with ESX 8 on the physical host