Skip to content

fix(hyperv): correct dynamic memory allocation based on vagrant spec - #13825

Open
nghiahl-sysadmin wants to merge 1 commit into
hashicorp:mainfrom
nghiahl-sysadmin:fix-hyperv-startup-memory-spec
Open

fix(hyperv): correct dynamic memory allocation based on vagrant spec#13825
nghiahl-sysadmin wants to merge 1 commit into
hashicorp:mainfrom
nghiahl-sysadmin:fix-hyperv-startup-memory-spec

Conversation

@nghiahl-sysadmin

Copy link
Copy Markdown

Align the plugin with Vagrant documentation:
"memory (integer) - Number of megabytes allocated to VM at startup. If maxmemory is set, this will be amount of memory allocated at startup."

  • Fix dynamic memory logic to respect the documentation where memory represents the allocated memory at startup.
  • Override MemoryMaximumBytes with $MaxMemory when specified.

Align the plugin with Vagrant documentation:
"memory (integer) - Number of megabytes allocated to VM at startup. If maxmemory is set, this will be amount of memory allocated at startup."

- Fix dynamic memory logic to respect the documentation where `memory` represents the allocated memory at startup.
- Override `MemoryMaximumBytes` with `$MaxMemory` when specified.
@hashicorp-cla-app

hashicorp-cla-app Bot commented Jun 27, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@hashicorp-cla-app

Copy link
Copy Markdown

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant