[Feature]: Support sched.mem.enableNestedTiering = true for esx hosts on host with name tiering
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 30
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Description
Would it be possible to automate the addition of the sched.mem.enableNestedTiering = true option for ESX hosts during the build in order to support "NVMe Tiering for Nested ESX VM" as shown here: https://williamlam.com/2026/05/vcf-9-1-comprehensive-esx-configuration-workarounds-for-lab-deployments.html
Use case / Motivation
Just saves a step of having to add it later, reboot the ESX hosts etc after they have already been built and running all the components.
Proposed solution
Add another flag to New-HoloDeckInstance perhaps
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the New-HoloDeckInstance entry point mentioned in the issue and trace how ESX hosts are configured during the build. Review the linked NVMe Tiering for Nested ESX VM context and identify how a flag could apply the setting to hosts whose names match tiering. Done means the option is applied automatically during the build, before the hosts and components are running.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100